From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] Editing filesystem files
Date: Thu, 10 Apr 2008 08:31:03 +1000 [thread overview]
Message-ID: <20080409223102.GA4582@cloud.net.au> (raw)
In-Reply-To: <11ea01c89a37$87cb1010$f52f9e86@LPSC0173W>
On Wed, Apr 09, 2008 at 01:47:41PM +0200, Guillaume Dargaud wrote:
> Following up on this, when do the files in target/generic/target_skeleton
> get copied in project_build_powerpc/genepy/root ?
>
> It seems to happen the very first time in run make and then never again, no
> matter what I try (even after make clean).
Yes that's my experience.
> The documentation says:
> "So simply rebuilding the image by running make should propagate any new
> changes to the image."
> but I just don't see that happening, even if I "rm -rf
> project_build_powerpc/genepy/root" (only dynamically created files get
> rebuilt there then).
If you delete the root it should re-copy the target_skeleton, but you
may find that lots of other files don't get reinstalled (particularly
some of the toolchain libraries).
Unfortunately some of the packages don't use files in the root as their
test, but stamp files elsewhere in the build tree. Or they don't depend
on enough files in the root...
With an external toolchain it's safe to delete most of the root I've
found.
Dependencies between files in the root and the target_skeleton would be
preferable. This would detect everything other than file deletions.
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next prev parent reply other threads:[~2008-04-09 22:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 14:29 [Buildroot] Editing filesystem files Guillaume Dargaud
2008-04-09 11:47 ` Guillaume Dargaud
2008-04-09 22:31 ` Hamish Moffatt [this message]
2008-04-10 11:43 ` Guillaume Dargaud
2008-04-12 9:22 ` Hamish Moffatt
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=20080409223102.GA4582@cloud.net.au \
--to=hamish@cloud.net.au \
--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