<div dir="ltr"><div>Hi, Andre:<br></div><div>The reason for needing this multiconfig to be in OVERRIDES, for me, is the scenario that I have one recipe but some variables/tasks in it are different for multiconfig, for instance:</div><div><br></div><div>do_install-mc-default () {}</div><div><br></div><div>do_install-mc-foo() {}</div><div><br></div><div>and I do not want split them into several almost same recipes with only one task different.</div><div><br></div><div>//Ming Liu</div><div class="gmail_extra"><br><div class="gmail_quote">2018-06-12 1:15 GMT+02:00 Andre McCurdy <span dir="ltr"><<a href="mailto:armccurdy@gmail.com" target="_blank">armccurdy@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Mon, Jun 11, 2018 at 4:34 AM, <<a href="mailto:liu.ming50@gmail.com">liu.ming50@gmail.com</a>> wrote:<br>
> From: Ming Liu <<a href="mailto:liu.ming50@gmail.com">liu.ming50@gmail.com</a>><br>
><br>
> This is useful when the users want different variables/tasks when using<br>
> multiconfig.<br>
<br>
</span>Isn't the idea of multiconfig to select between configurations which<br>
already fully define all necessary over-rides?<br>
<br>
If a particular multiconfig build needs a custom over-ride then the<br>
multiconfig can append to OVERRIDES (or MACHINEOVERRIDES etc, as<br>
appropriate) directly.<br>
<br>
ie to avoid confusion isn't it good if building with a multiconfig<br>
enabled is always equivalent to building with the contents of the<br>
multiconfig file copied directly in local.conf?<br>
<div class="HOEnZb"><div class="h5"><br>
> Signed-off-by: Ming Liu <<a href="mailto:liu.ming50@gmail.com">liu.ming50@gmail.com</a>><br>
> ---<br>
> meta/conf/bitbake.conf | 2 +-<br>
> 1 file changed, 1 insertion(+), 1 deletion(-)<br>
><br>
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf<br>
> index 3b2ef9f..0c803d5 100644<br>
> --- a/meta/conf/bitbake.conf<br>
> +++ b/meta/conf/bitbake.conf<br>
> @@ -731,7 +731,7 @@ DISTRO_NAME ??= "OpenEmbedded"<br>
> # And finally '<foo>_forcevariable' overrides any standard variable, with the highest priority.<br>
> # This works for functions as well, they are really just variables.<br>
> #<br>
> -OVERRIDES = "${TARGET_OS}:${TRANSLATED_<wbr>TARGET_ARCH}:pn-${PN}:${<wbr>MACHINEOVERRIDES}:${<wbr>DISTROOVERRIDES}:${<wbr>CLASSOVERRIDE}${LIBCOVERRIDE}:<wbr>forcevariable"<br>
> +OVERRIDES = "${TARGET_OS}:${TRANSLATED_<wbr>TARGET_ARCH}:pn-${PN}:${<wbr>MACHINEOVERRIDES}:${<wbr>DISTROOVERRIDES}:${<wbr>CLASSOVERRIDE}${LIBCOVERRIDE}:<wbr>mc-${BB_CURRENT_MC}:<wbr>forcevariable"<br>
> LIBCOVERRIDE ?= ""<br>
> CLASSOVERRIDE ?= "class-target"<br>
> DISTROOVERRIDES ?= "${@d.getVar('DISTRO') or ''}"<br>
> --<br>
> 2.7.4<br>
><br>
</div></div><span class="HOEnZb"><font color="#888888">> --<br>
> ______________________________<wbr>_________________<br>
> Openembedded-core mailing list<br>
> <a href="mailto:Openembedded-core@lists.openembedded.org">Openembedded-core@lists.<wbr>openembedded.org</a><br>
> <a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" rel="noreferrer" target="_blank">http://lists.openembedded.org/<wbr>mailman/listinfo/openembedded-<wbr>core</a><br>
</font></span></blockquote></div><br></div></div>