From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] which templates are used?
Date: Tue, 19 Apr 2011 22:25:47 +0200 [thread overview]
Message-ID: <20110419222547.3c28192b@surf> (raw)
In-Reply-To: <4DA3976B.40807@gmail.com>
On Mon, 11 Apr 2011 17:06:03 -0700
Steve Calfee <stevecalfee@gmail.com> wrote:
> BR2_ROOTFS_POST_BUILD_SCRIPT
That's also what I use. Instead of making modifications to
fs/skeleton/, or completely duplicating that skeleton, my post build
script :
*) Copies some additional files (which I typically store and version
control in board/<mycompany>/<myproduct>)
*) Adjust some files from the skeleton. It does this in a way that
allows to re-run make several times without screwing things. For
example, if I need to add a new line at the end of a file
(like /etc/fstab), I first test that this line hasn't already been
added, in order to avoid duplicates.
This technique has several advantages :
*) You don't change the default skeleton, which would mess things up
next time you upgrade Buildroot ;
*) You don't duplicate the entire default skeleton, which prevents you
from taking advantages of new things in the skeleton if you upgrade
Buildroot ;
*) As the post build script is executed at every 'make' invocation,
you don't have to 'make clean ; make' to see the effect of your post
build script changes.
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-04-19 20:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 20:10 [Buildroot] which templates are used? Michael Burghart
2011-04-11 20:52 ` Michael Burghart
2011-04-11 21:14 ` Bjørn Forsman
2011-04-11 23:34 ` Michael J. Hammel
2011-04-12 6:42 ` Patryk Benderz
2011-04-12 17:54 ` Bjørn Forsman
2011-04-11 21:20 ` Daniele Salvatore Albano
2011-04-12 0:06 ` Steve Calfee
2011-04-12 13:01 ` Michael S. Zick
2011-04-12 16:52 ` Steve Calfee
2011-04-19 20:25 ` Thomas Petazzoni [this message]
2011-04-20 16:59 ` Bjørn Forsman
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=20110419222547.3c28192b@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