From: Mike Looijmans <mike.looijmans@topic.nl>
To: <yocto@yoctoproject.org>
Subject: Re: parallel build of multiple machine/os?
Date: Thu, 11 Dec 2014 07:55:11 +0100 [thread overview]
Message-ID: <54893FCF.6010303@topic.nl> (raw)
In-Reply-To: <FABD1EBC-088D-41C9-8CD0-F7D2D4493896@gmail.com>
On 12/10/2014 08:00 PM, Khem Raj wrote:
>
>> On Dec 10, 2014, at 10:52 AM, Koehler, Yannick (HP Networking) <yannick.koehler@hp.com> wrote:
>>
>> Can Yocto build for example in a single bitbake call an image for x86, ppc, arm, others? Or is the call to bitbake limited to a single architecture? And if so, how?
>>
>> I see that lots of *-native package are built, and I guess is that for each machine/os those would be reused, as such, it appears it would be a benefit to be able to build multiple package version for different architecture/distro/machine in a single invocation of bitbake.
>
> parallel multi-machine builds have been discussed but not thought of worth doing. you could however share
> lot of common packages among machines sequentially.
>
> [...]
A more convincing use-case for multi-machine building is the emerging of
"hybrids". The little/big architecture that puts different versions of ARM
CPUs into a single machine is one example, the OMAPs with the DSP and PRUs are
another. Boards with FPGAs can have several CPU architectures running on a
single board. One could imagine that one would want to build the software for
all these subsystems in a single call, and that one bitbake process would be
managing that the build system gets properly used.
Currently, these hybrids have to invoke bitbake for each subsystem, probably
needlessly regenerating binaries, and once more for the one image to find them
all and in darkness bind them...
Met vriendelijke groet / kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
Telefax: (+31) (0) 499 33 69 70
E-mail: mike.looijmans@topic.nl
Website: www.topic.nl
Please consider the environment before printing this e-mail
Topic zoekt gedreven (embedded) software specialisten!
http://topic.nl/vacatures/topic-zoekt-software-engineers/
next prev parent reply other threads:[~2014-12-11 6:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 18:52 parallel build of multiple machine/os? Koehler, Yannick (HP Networking)
2014-12-10 19:00 ` Khem Raj
2014-12-10 19:27 ` Maciek Borzecki
2014-12-11 6:55 ` Mike Looijmans [this message]
2014-12-11 19:42 ` Mark Hatle
2014-12-12 6:24 ` Mike Looijmans
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=54893FCF.6010303@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=yocto@yoctoproject.org \
/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.