Hi, Richard: I saw your comment as follows:
> This adds "" in OVERRIDES in the default case. Whilst I think (but am not 100% sure) we fixed bitbake not to break on such a value, I'm not convinced adding empty elements to it is a good idea and this did used to break things. No, it will add "default" to OVERRIDES in the default case. //Ming Liu 2018-06-09 17:24 GMT+02:00 <[email protected]>: > From: Ming Liu <[email protected]> > > This is useful when the users want different variables/tasks when using > multiconfig. > > Signed-off-by: Ming Liu <[email protected]> > --- > meta/conf/bitbake.conf | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf > index 3b2ef9f..8b2555b 100644 > --- a/meta/conf/bitbake.conf > +++ b/meta/conf/bitbake.conf > @@ -731,7 +731,7 @@ DISTRO_NAME ??= "OpenEmbedded" > # And finally '<foo>_forcevariable' overrides any standard variable, with > the highest priority. > # This works for functions as well, they are really just variables. > # > -OVERRIDES = "${TARGET_OS}:${TRANSLATED_TARGET_ARCH}:pn-${PN}:${ > MACHINEOVERRIDES}:${DISTROOVERRIDES}:${CLASSOVERRIDE}${LIBCOVERRIDE}: > forcevariable" > +OVERRIDES = "${TARGET_OS}:${TRANSLATED_TARGET_ARCH}:pn-${PN}:${ > MACHINEOVERRIDES}:${DISTROOVERRIDES}:${CLASSOVERRIDE}${LIBCOVERRIDE}: > ${BB_CURRENT_MC}:forcevariable" > LIBCOVERRIDE ?= "" > CLASSOVERRIDE ?= "class-target" > DISTROOVERRIDES ?= "${@d.getVar('DISTRO') or ''}" > -- > 2.7.4 > >
-- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
