Re: multi MACHINE build for same DISTRO_ARCH

[Henning Schild <henning.schild@siemens.com>]

Hi,

the key is to get the split between machine and distro configs right.
And to make sure all your recipes create generic enough packages that
can be shared or differ in name/version where not.

The great sharing potential, reducing build time and size, but also
means a high risk of false sharing if you make a mistake. I
personally avoid multiconfig builds for that reason.

Henning

Am Mon, 1 Jul 2019 16:41:36 +0200
schrieb 'Benedikt Niedermayr' via isar-users
<isar-users@googlegroups.com>:

> 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?
> 
> 
> 
> Thanks,
> 
> Benni
> 
> 
> 
>