Re: Why does Isar build multiple configs in one OUTDIR?

[Jan Kiszka <jan.kiszka@siemens.com>]

On 2017-08-10 10:25, Baurzhan Ismagulov wrote:
>>> If we returned to the pre-multiconfig way of having separate build
>>> dirs, automating building all products in the repo would require
>>> gluing those two steps together. How? Shell with sed patching of
>>> local.conf? 
>>
>> Bitbake Layering. Maybe combined with git submodules or kas.
> 
> Maybe? Please specify how you suggest to build images for ICH WE and PE.
> 
> The fact is, the products are already layered and split in different git repos.
> Apart from the fact that Isar predates kas and solves the problem well: I'd use
> kas for cloning disparate repos (like the repo tool in Android), not for build
> dir management.

kas manages config dependencies that are under the same release regime
in a single file. It also provides a clean, archiveable build
environment, which is even more important with OE.

If your production generates multiple variants from a single release,
there is surely a value in exploiting the new multiconfig feature of
bitbake. It's an optimization that can save a hand full of lines in your
CI script and likely quite a bit cycles of your CI server. I see it as
an added value. But as Isar is already wrapped around it, no longer
works without it (because that would mean duplicate maintenance), we
have to make sure to support it, including a better support in kas.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux