Arha, good suggestion, will do that in V2. //Ming Liu
2018-06-11 10:51 GMT+02:00 Peter Kjellerstedt <[email protected]>: > > -----Original Message----- > > From: [email protected] > > [mailto:[email protected]] On Behalf Of > > Richard Purdie > > Sent: den 10 juni 2018 21:29 > > To: Ming Liu <[email protected]>; OE-core <openembedded- > > [email protected]> > > Subject: Re: [OE-core] [PATCH] bitbake.conf: add BB_CURRENT_MC to > > OVERRIDES > > > > On Sun, 2018-06-10 at 20:45 +0200, Ming Liu wrote: > > > 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. > > > > That is even worse, we do not want to add "default" to overrides since > > any variable containing that word would then be at risk of weird > > breakage. > > > > Cheers, > > > > Richard > > You could add it as ":mc-${BB_CURRENT_MC}:" to OVERRIDES to avoid the > ambiguity, similar to the pn- and df- prefixes used for recipe names > and distro features. > > //Peter > >
-- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
