From: Steve Calfee <stevecalfee@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Where does post-build script belong?
Date: Tue, 28 Feb 2012 13:29:53 -0800 [thread overview]
Message-ID: <4F4D4751.1030906@gmail.com> (raw)
In-Reply-To: <jijfkp$qv0$1@dough.gmane.org>
On 02/28/2012 01:06 PM, Grant Edwards wrote:
> On 2012-02-28, Arnout Vandecappelle<arnout@mind.be> wrote:
>> On Tuesday 21 February 2012 14:54:47 Grant Edwards wrote:
>> [snip]
>>> I don't want to replace the default skeleton. I want to add some
>>> files to it, and possible modify a few. The documentation describes
>>> two ways to do that:
>>>
>>> 1) package/customize
>>>
>>> 2) post-build script
>>>
>>> I'm told 1) is now depricated, so I'm switching to 2).
>>>
>>> Where under board/mycompany/myproduct do you put "extra" files that
>>> will be added to the standard skeleton?
>> I put it in board/mycompany/myproduct/skeleton. Although
>> rootfs-additions would be a better name than skeleton.
> Ah, perhaps I've misunderstood what a custom skeleton was for the past
> several years. I thought it was the basis for the filesystem. Is the
> custom skeleton something that's _added_ on top of the default
> skeleton rather than used in place of it?
>
Perhaps, but it is your script. If you want to completely replace the
existing skeleton you can, but I think it makes more sense to just
overlay new stuff on top of the default skeleton. This makes your new
skeleton much smaller, and since it is run after every build, you don't
have to wonder if changes make it to the target filesystem, it always does.
Regards, Steve
next prev parent reply other threads:[~2012-02-28 21:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 20:41 [Buildroot] Where does post-build script belong? Grant Edwards
2012-02-20 21:00 ` J.C. Woltz
2012-02-20 21:45 ` Grant Edwards
2012-02-21 8:44 ` Luca Ceresoli
2012-02-21 14:54 ` Grant Edwards
2012-02-28 20:38 ` Arnout Vandecappelle
2012-02-28 21:06 ` Grant Edwards
2012-02-28 21:29 ` Steve Calfee [this message]
2012-02-28 21:36 ` Grant Edwards
2012-02-28 22:06 ` Steve Calfee
2012-02-28 22:18 ` Grant Edwards
2012-03-16 21:30 ` Peter Korsgaard
2012-02-28 22:19 ` Arnout Vandecappelle
2012-02-29 7:41 ` Thomas De Schampheleire
2012-03-16 21:32 ` Peter Korsgaard
2012-02-28 22:18 ` Arnout Vandecappelle
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=4F4D4751.1030906@gmail.com \
--to=stevecalfee@gmail.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