<div dir="ltr">Yes, that is true, but then I will need have a mc-default override set in local.conf any way, since I need distinguish the build for all multiconfigs, that makes me think it'd better to have a single mc-${BB_CURRENT_MC} set in OVERRIDES.<div><br></div><div>//Ming Liu </div></div><div class="gmail_extra"><br><div class="gmail_quote">2018-06-12 19:49 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 Tue, Jun 12, 2018 at 4:43 AM, Ming Liu <<a href="mailto:liu.ming50@gmail.com">liu.ming50@gmail.com</a>> wrote:<br>
> Hi, Andre:<br>
> The reason for needing this multiconfig to be in OVERRIDES, for me, is the<br>
> scenario that I have one recipe but some variables/tasks in it are different<br>
> for multiconfig, for instance:<br>
><br>
> do_install-mc-default () {}<br>
><br>
> do_install-mc-foo() {}<br>
><br>
> and I do not want split them into several almost same recipes with only one<br>
> task different.<br>
<br>
</span>Yes, that's clear. But the question is whether you can make the<br>
over-rides you need self contained within the multiconfig config file?<br>
<br>
e.g. to enable an over-ride when you build with multiconfig foo, add:<br>
<br>
OVERRIDES .= ":mc-foo"<br>
<br>
to foo.conf<br>
<br>
If it works, then it gives you more flexibility - you can pick your<br>
own over-ride naming, define multiple over-rides per multiconfig, etc.<br>
<div class="HOEnZb"><div class="h5"><br>
> //Ming Liu<br>
><br>
> 2018-06-12 1:15 GMT+02:00 Andre McCurdy <<a href="mailto:armccurdy@gmail.com">armccurdy@gmail.com</a>>:<br>
>><br>
>> 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>
>> 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>
>><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,<br>
>> > with the highest priority.<br>
>> > # This works for functions as well, they are really just variables.<br>
>> > #<br>
>> > -OVERRIDES =<br>
>> > "${TARGET_OS}:${TRANSLATED_<wbr>TARGET_ARCH}:pn-${PN}:${<wbr>MACHINEOVERRIDES}:${<wbr>DISTROOVERRIDES}:${<wbr>CLASSOVERRIDE}${LIBCOVERRIDE}:<wbr>forcevariable"<br>
>> > +OVERRIDES =<br>
>> > "${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>
>> > --<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>
><br>
><br>
</div></div></blockquote></div><br></div>