From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot and top-level parallel make
Date: Sat, 30 Jun 2012 14:48:34 +0200 [thread overview]
Message-ID: <4FEEF5A2.7060506@mind.be> (raw)
In-Reply-To: <CA+wH296drhV6yie5+79Y38qLmo_5cE1=3qaOrw5jbyCJ5mEMog@mail.gmail.com>
On 06/28/12 14:34, Alex Bradbury wrote:
> As I understand it, buildroot will allow parallelism while building
> individual packages yet does not support "top-level parallel make".
> i.e. it is not possible to build multiple packages in parallel. I
> found a reference to this problem at http://lwn.net/Articles/416916/
> and it was also listed as a WIP in the "cross build systems: present
> and future" slides from 2010.
>
> I was wondering what the outcome of experiments to allow top-level
> parallelism were? What are the major barriers to allowing this? Is it
> still something seen as feasible to add to buildroot, or is it looking
> like it would add too much complexity?
AFAIK nobody is actually working on this. Myself I have had a little
thought about it before, and the main problem seems that there are a few
targets in the top-level Makefile that depend on the left-to-right
evaluation order of dependencies.
It would of course be difficult to verify that a top-level parallel make
works, but now we have the autobuild system it can be done...
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-06-30 12:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 12:34 [Buildroot] Buildroot and top-level parallel make Alex Bradbury
2012-06-30 12:48 ` Arnout Vandecappelle [this message]
2012-06-30 22:22 ` Alex Bradbury
2012-07-04 12:20 ` Alex Bradbury
2012-07-13 10:34 ` Alex Bradbury
2012-07-14 21:37 ` Arnout Vandecappelle
2012-07-15 20:16 ` Thomas Petazzoni
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=4FEEF5A2.7060506@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