From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] howto incorporate buildroot into an autobuild
Date: Tue, 13 Nov 2012 22:04:54 +0100 [thread overview]
Message-ID: <50A2B5F6.2040106@mind.be> (raw)
In-Reply-To: <CAHqTa-2vZ_xs26oCX8kFtgQQzGaOcLWG=r2S+hsmUi1E6WZ2Vg@mail.gmail.com>
On 13/11/12 06:02, Avery Pennarun wrote:
> I also severely hacked up buildroot to be able to build multiple
> packages in parallel on a multicore machine; this makes builds
> typically 2-3x faster on our setup, and probably even more so if you
> use a really fast disk (SSD RAID?) and lots of RAM and multiple CPUs.
> You can see our hacked-up version here:
> http://gfiber.googlesource.com/buildroot
>
> Beware, however, as it may burn your eyes. Someday I would like to
> clean up the parallelism patches and submit them here.
Wow! There are a couple of great ideas in that repository. I certainly
wouldn't mind seeing some of these things upstreamed. Like the shuffle
thing, that would be really great for the autobuilders.
Regards,
Arnout
--
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: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-11-13 21:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 0:47 [Buildroot] howto incorporate buildroot into an autobuild John Stile
2012-11-13 5:02 ` Avery Pennarun
2012-11-13 21:04 ` Arnout Vandecappelle [this message]
2012-11-13 8:45 ` Thomas Petazzoni
2012-11-13 20:43 ` 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=50A2B5F6.2040106@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 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.