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

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

On 2017-08-11 14:20, Baurzhan Ismagulov wrote:
> On Thu, Aug 10, 2017 at 12:37:01PM -0400, Jan Kiszka wrote:
>> 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.
> 
> Just to ensure we are talking about the same thing: BitBake's multiconfig
> feature is a means of building for multiple MACHINE + DISTRO configurations in
> a single run without having to deal with local.conf in between. Multiconfig and
> local.conf are completely equivalent and mutually interchangeable. BitBake and
> Isar support either without requiring the other, or both. In the same build

Theoretically, Isar could still build without multiconfig. But
practically, more and more information is now only in
meta-isar/conf/multiconfig, and one would has to copy that out into an
own local.conf (or a kas config).

But focusing on one method is fine, we should just avoid confusions
regarding the other.

Jan

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