From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] Editing filesystem files
Date: Sat, 12 Apr 2008 19:22:10 +1000 [thread overview]
Message-ID: <20080412092210.GA15915@cloud.net.au> (raw)
In-Reply-To: <005b01c89b00$1630eeb0$ad289e86@LPSC0173W>
On Thu, Apr 10, 2008 at 01:43:20PM +0200, Guillaume Dargaud wrote:
>
> > Dependencies between files in the root and the target_skeleton would be
> > preferable. This would detect everything other than file deletions.
>
> Yes, but it would be quite heavy to put it all in a make file, with the risk
> of forgetting something. I'm okay with the idea of the root being rebuilt
There's no need to list all the files in the Makefile; you can use
$(wildcard ...) to generate the list dynamically. Although I haven't
tried to do this for a whole tree.
> from scratch, but how do you trigger that ? As you say, even deleting it
> completely won't copy some of the skeleton back. What can we 'touch' to make
> this happen ?
With external toolchain it seems to be safe to delete most (if not all)
of the project_build_xyz/abc/root directory. I don't have a good answer
to your question though. Personally I would like to have proper
dependencies so that I don't need to do an explicit re-copy operation.
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
prev parent reply other threads:[~2008-04-12 9:22 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
2008-04-10 11:43 ` Guillaume Dargaud
2008-04-12 9:22 ` Hamish Moffatt [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=20080412092210.GA15915@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.