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

[Baurzhan Ismagulov <ibr@radix50.net>]

On Sat, Aug 19, 2017 at 09:53:54AM -0400, Jan Kiszka wrote:
> 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).

Good catch, thanks. Indeed, building with the default local.conf produces a
working image, albeit the kernel / initrd is not extracted.
https://github.com/ilbers/isar/issues/29


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

As multiconfig is relatively new in bitbake, many people are not familiar with
it. Besides, local.conf would save people with one config the cumbersome
multiconfig syntax.

I think keeping local.conf working shouldn't cost too much effort -- in the
worst case, the vars added to multiconfig should also be added to local.conf.
Maybe we manage to come up with some standard customization file location
without having to repeat ourselves.


With kind regards,
Baurzhan.