search

siemens / kas

Setup tool for bitbake based projects
MIT License
363 stars 147 forks source link

multiconfig syntax is not documented #7

Closed moto-timo closed 5 years ago

moto-timo commented 5 years ago

Please let us know how to use the multiconfig:* feature. Do we put conf/multiconfig/foo.conf in local layer (meta-custom)?

moto-timo commented 5 years ago

The syntax is:

target:
  - <target>
  - multiconfig:<multiconfig_name>:<target>

Where you would have conf/multiconfig/<multiconfig_name>.conf in your local layer (meta-custom).

For example:

target:
  - core-image-base
  - multiconfig:foo:core-image-minimal

For more details on multiconfig, see the Yocto Project documentation.

jan-kiszka commented 5 years ago

Yes, that multiconfig "just works" is not explicitly documented, only indirectly via changelog and format history. Feel free to propose something for the user doc. Just note that we have email-based patch workflow via the mailing list.

vivien commented 3 years ago

This means that BBMULTICONFIG won't be set if target doesn't contain an mc: prefix. This can be problematic if the recipe being built contains do_task[mcdepends] = "mc:foo:bar:image:task".

Defining BBMULTICONFIG manually in _local_confheader isn't a solution because kas wouldn't have copied the multiconfig files to the build directory.

Am I correct?

jan-kiszka commented 3 years ago

Just realized the duplication to #30... Please comment at least on the active issue or - even better in this case - open a new one for a new issues.

To answer your question in advance: yes, this use case is likely not supported because it was not foreseen back then.