From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] How to add share/zoneinfo to my Linux target
Date: Tue, 15 Nov 2011 22:25:07 +0100 [thread overview]
Message-ID: <20111115222507.5fe3b85b@skate> (raw)
In-Reply-To: <C5029C549AA03148AF1B73C0F27DC86D021CEDCB@mse2003.vanteonrdc.vanteon.com>
Le Tue, 15 Nov 2011 15:29:14 -0500,
"Thireos, Mike" <mthireos@vanteon.com> a ?crit :
> We are using buildroot with linux 2.6.31 and glibc to build for our
> target platform. I see the zoneinfo directory in the staging folder,
> but I can't seem to find any configuration option to get it into my
> target file system. I also tried adding it to the skeleton folder
> with no luck.
There is no dedicated option to do that. However, Buildroot provides
you with the BR2_POST_BUILD_SCRIPT option, which can be set to the path
to a script that gets executed after all packages have been installed
but *before* the root filesystem images are generated.
Therefore, you can write a custom script that makes various
modifications on the target root filesystem, including copying the
zoneinfo informations.
See http://elinux.org/images/2/2a/Using-buildroot-real-project.pdf for
more details on using the post build script, and example of usage.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-11-15 21:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 20:29 [Buildroot] How to add share/zoneinfo to my Linux target Thireos, Mike
2011-11-15 21:25 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-11-15 18:10 Thireos, Mike
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111115222507.5fe3b85b@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox