From: Benedikt Niedermayr <benbrenson89@googlemail.com>
To: Jan Kiszka <jan.kiszka@siemens.com>, isar-users@googlegroups.com
Subject: Re: multi MACHINE build for same DISTRO_ARCH
Date: Mon, 1 Jul 2019 19:03:11 +0200 [thread overview]
Message-ID: <dc8111a5-a4f4-f3e0-faab-20d7b3caccd7@googlemail.com> (raw)
In-Reply-To: <626786fb-3b6d-d569-7429-ac1a5a05d685@siemens.com>
Am 01.07.19 um 16:51 schrieb Jan Kiszka:
> On 01.07.19 16:41, 'Benedikt Niedermayr' via isar-users wrote:
>> Hi guys,
>>
>> before I send some patches to you I would like to discuss this a bit.
>>
>> The problem is to run multi machine builds for the same DISTRO_ARCH.
>>
>> We have for example a BSP layer which supports imx6, imx7 and imx8
>> architectures, and we like to be able to run
>>
>> those builds within a single bitbake command:
>>
>>
>> bitbake multiconfig:imx6-stretch:isar-image-base \
>>
>> multiconfig:imx7-stretch:isar-image-base \
>>
>> multiconfig:imx8-stretch:isar-image-base
>>
>>
>> The build runs fine if DISTRO_ARCH differs between targets. But it
>> does not run successfully if only MACHINE differs and DISTRO_ARCH is
>> the same.
>>
>>
>> I think running multi machine build within one bitbake build folder
>> makes a lot of sense, especially when it comes to build time and CI.
>>
>> I don't like it to create a new build folder for every MACHINE,
>> although everything (rootfs, buildchroot, etc.) stays almost the same
>> among DISTRO_ARCHs.
>>
>>
>>
>> Is anybody familiar with this behavior?
>>
>
> You may want to study https://github.com/siemens/jailhouse-images for
> a working pattern. May not be the only possible one, but already that
> required some careful balancing.
>
> Jan
>
Hi Jan,
thanks.
I will take a look at it and reply ASAP.
next prev parent reply other threads:[~2019-07-01 17:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 14:41 Benedikt Niedermayr
2019-07-01 14:51 ` Jan Kiszka
2019-07-01 17:03 ` Benedikt Niedermayr [this message]
2019-07-02 10:21 ` Henning Schild
2019-07-05 16:12 ` Baurzhan Ismagulov
2019-07-10 18:52 ` benbrenson89
2019-07-10 19:09 ` Jan Kiszka
2019-07-11 17:09 ` Henning Schild
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=dc8111a5-a4f4-f3e0-faab-20d7b3caccd7@googlemail.com \
--to=benbrenson89@googlemail.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
/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