From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] asking for advice on improving our buildroot setup
Date: Thu, 21 Jul 2011 09:53:49 +0200 [thread overview]
Message-ID: <201107210953.49838.arnout@mind.be> (raw)
[Late reply, but probably still relevant]
On Thursday 07 July 2011 12:09:20, Sven Neumann wrote:
> As you can imagine this build consumes a lot of time and disk space.
> Currently I can think of two ways to improve this:
>
> (1) Add an initial step that builds a toolchain and then use that
> toolchain from the following steps. This would save the time
> to rebuild the toolchain for each of the steps.
>
> (2) Combine all steps and build different rootfs from within the
> same buildroot tree. I read that this would be supported. But
> I would like to get advice from you first. Is there a chance
> that this will work for the described setup?
If your build host can be upgraded to a recent kernel with btrfs, you could
do the following:
* Create a basic buildroot configuration with the stuff that is relevant for
all builds.
* cp --reflink -a output output-specific-target
* make specific-target-config O=output-specific-target
=> this will add the additional stuff to output-specific-target and (re)
create the images.
Because of the --reflink, no additional disk space will be used for the copy
of the toolchain etc.
Regards,
Arnout
--
Arnout Vandecappelle Senior Embedded Software Architect
arnout dot vandecappelle at essensium com +32-16-286540 +32-478-010353
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 31BB CF53 8660 6F88 345D 54CC A836 5879 20D7 CF43
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 31BB CF53 8660 6F88 345D 54CC A836 5879 20D7 CF43
next reply other threads:[~2011-07-21 7:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 7:53 Arnout Vandecappelle [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-07-07 10:09 [Buildroot] asking for advice on improving our buildroot setup Sven Neumann
2011-07-07 11:42 ` Peter Korsgaard
2011-07-07 11:59 ` Thomas Petazzoni
2011-07-07 12:22 ` Daniel Mack
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=201107210953.49838.arnout@mind.be \
--to=arnout@mind.be \
--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