Re: [OE-core] [PATCH] bitbake.conf, module.bbclass: Support opting out of legacy EXTRA_OEMAKE

On Thu, Nov 12, 2015 at 4:10 AM, Mike Crowe wrote: > On Friday 06 November 2015 at 10:30:04 +, Mike Crowe wrote: >> It would be great to get to the point that EXTRA_OEMAKE is empty by default >> but I imagine that the experts are already aware of the difficulties with >>

Re: [OE-core] [PATCH] bitbake.conf, module.bbclass: Support opting out of legacy EXTRA_OEMAKE

On Friday 06 November 2015 at 10:30:04 +, Mike Crowe wrote: > It would be great to get to the point that EXTRA_OEMAKE is empty by default > but I imagine that the experts are already aware of the difficulties with > doing this which is why the current value has lasted so long. I had a go at

Re: [OE-core] [PATCH] bitbake.conf, module.bbclass: Support opting out of legacy EXTRA_OEMAKE

On Friday 06 November 2015 at 01:16:46 -0800, Andre McCurdy wrote: > On Thu, Nov 5, 2015 at 6:47 AM, Mike Crowe wrote: > > Give recipes and classes the ability to opt out of EXTRA_OEMAKE > > containing the legacy value without removing other recipe-specific or > > local

Re: [OE-core] [PATCH] bitbake.conf, module.bbclass: Support opting out of legacy EXTRA_OEMAKE

On Thu, Nov 5, 2015 at 6:47 AM, Mike Crowe wrote: > Give recipes and classes the ability to opt out of EXTRA_OEMAKE > containing the legacy value without removing other recipe-specific or > local additions. Isn't this possible already from within a recipe or class by using

Re: [OE-core] [PATCH] bitbake.conf, module.bbclass: Support opting out of legacy EXTRA_OEMAKE

On Fri, Nov 6, 2015 at 6:18 AM, Martin Jansa wrote: > On Fri, Nov 06, 2015 at 10:30:04AM +, Mike Crowe wrote: > > On Friday 06 November 2015 at 01:16:46 -0800, Andre McCurdy wrote: > > > On Thu, Nov 5, 2015 at 6:47 AM, Mike Crowe wrote: > > > > Give

Re: [OE-core] [PATCH] bitbake.conf, module.bbclass: Support opting out of legacy EXTRA_OEMAKE

On Fri, Nov 06, 2015 at 07:59:32AM -0700, Christopher Larson wrote: > On Fri, Nov 6, 2015 at 6:18 AM, Martin Jansa wrote: > > > On Fri, Nov 06, 2015 at 10:30:04AM +, Mike Crowe wrote: > > > On Friday 06 November 2015 at 01:16:46 -0800, Andre McCurdy wrote: > > > > On

Re: [OE-core] [PATCH] bitbake.conf, module.bbclass: Support opting out of legacy EXTRA_OEMAKE

On Fri, Nov 06, 2015 at 10:30:04AM +, Mike Crowe wrote: > On Friday 06 November 2015 at 01:16:46 -0800, Andre McCurdy wrote: > > On Thu, Nov 5, 2015 at 6:47 AM, Mike Crowe wrote: > > > Give recipes and classes the ability to opt out of EXTRA_OEMAKE > > > containing the legacy

Re: [OE-core] [PATCH] bitbake.conf, module.bbclass: Support opting out of legacy EXTRA_OEMAKE

> On Nov 5, 2015, at 6:47 AM, Mike Crowe wrote: > > export MAKE = "make" > -EXTRA_OEMAKE = "-e MAKEFLAGS=" > +EXTRA_OEMAKE_LEGACY = "-e MAKEFLAGS=" > +EXTRA_OEMAKE = "${EXTRA_OEMAKE_LEGACY}" may be this should be a weak assignment. signature.asc Description: Message signed

Re: [OE-core] [PATCH] bitbake.conf, module.bbclass: Support opting out of legacy EXTRA_OEMAKE

On Thu, Nov 5, 2015 at 8:27 AM, Christopher Larson wrote: >> >> > >> > export MAKE = "make" >> > -EXTRA_OEMAKE = "-e MAKEFLAGS=" >> > +EXTRA_OEMAKE_LEGACY = "-e MAKEFLAGS=" >> > +EXTRA_OEMAKE = "${EXTRA_OEMAKE_LEGACY}" >> >> may be this should be a weak assignment. > > >

Re: [OE-core] [PATCH] bitbake.conf, module.bbclass: Support opting out of legacy EXTRA_OEMAKE

On Thu, Nov 5, 2015 at 9:23 AM, Khem Raj wrote: > > On Nov 5, 2015, at 6:47 AM, Mike Crowe wrote: > > > > export MAKE = "make" > > -EXTRA_OEMAKE = "-e MAKEFLAGS=" > > +EXTRA_OEMAKE_LEGACY = "-e MAKEFLAGS=" > > +EXTRA_OEMAKE = "${EXTRA_OEMAKE_LEGACY}" > > may

[OE-core] [PATCH] bitbake.conf, module.bbclass: Support opting out of legacy EXTRA_OEMAKE

Give recipes and classes the ability to opt out of EXTRA_OEMAKE containing the legacy value without removing other recipe-specific or local additions. The default value of EXTRA_OEMAKE="-e MAKEFLAGS=" is unfortunate. It causes breakage and unintended behaviour in various recipes. It is