From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot Patches I Use [2] - Build In Stages
Date: Tue, 9 Nov 2010 18:38:34 +0100 [thread overview]
Message-ID: <20101109183834.7dd0085f@surf> (raw)
In-Reply-To: <1289317805.30565.114.camel@tr-pentomino>
On Tue, 09 Nov 2010 07:50:05 -0800
Darcy Watkins <dwatkins@tranzeo.com> wrote:
> This patch is handy if you want to build in two stages. The first
> stage is to build up to before generating the rootfs. Then you could
> run other programs, scripts etc to generate stuff externally and add
> them to your target area. Then the second stage generates the rootfs
> images.
>
> This is handy for cases where you want to use an external set of
> scripts to drive the build process but have buildroot do some of the
> work so that you don't have to reinvent as many wheels.
Isn't BR2_ROOTFS_POST_BUILD_SCRIPT sufficient for this use case ?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2010-11-09 17:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 15:50 [Buildroot] Buildroot Patches I Use [2] - Build In Stages Darcy Watkins
2010-11-09 17:38 ` 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=20101109183834.7dd0085f@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 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.