From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] using target_skeleton directory
Date: Fri, 18 Dec 2009 10:28:10 +0100 [thread overview]
Message-ID: <20091218102810.5b81f330@surf> (raw)
In-Reply-To: <4B2B499F.6080203@diateam.net>
Hello Damien,
Le Fri, 18 Dec 2009 10:21:35 +0100,
Damien RANNOU <damien.rannou@diateam.net> a ?crit :
> I'm using buildroot-2009.11 and would like to have informations about
> target_skeleton directory. In the documentation it's said that I can
> customize my filesystem using |target/generic/target_skeleton/ |and
> just type "make" to have all my files copied into output/target, and
> the .tar.bz2 image file. But I made some tests, and it appears that
> files put in the /root directory (of target_skeleton) are only copied
> if I 'make distclean' before|.|
>
> Is it a bug ? A documentation problem ?
The target_skeleton directory is copied at the beginning of the
Buildroot build process to output/target/. If this copy has been done,
it is not done again unless you clean up everything. So the behaviour
you're having (need to clean up everything to get the skeleton copied
to the target directory) is expected.
You can try to remove output/build/.root and run make, it should
trigger the copy of the skeleton to the target directory. However, this
is untested, so there may be issues with this.
Sincerely,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2009-12-18 9:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 9:21 [Buildroot] using target_skeleton directory Damien RANNOU
2009-12-18 9:28 ` Thomas Petazzoni [this message]
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=20091218102810.5b81f330@surf \
--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