:27
> > To: Peter Kjellerstedt; Andre McCurdy; OE Core mailing list
> > Subject: Re: [OE-core] Using MACHINE_FEATURES in a native recipe
> >
> > On Fri, 2017-03-24 at 15:10 +, Peter Kjellerstedt wrote:
> > > Even though I agree this is a good change and that
Subject: Re: [OE-core] Using MACHINE_FEATURES in a native recipe
>
> On Fri, 2017-03-24 at 15:10 +, Peter Kjellerstedt wrote:
> > Even though I agree this is a good change and that it should be done,
> > I wonder if we can either hold it off until after Pyro has been
> >
On Fri, 2017-03-24 at 15:10 +, Peter Kjellerstedt wrote:
> Even though I agree this is a good change and that it should be done,
> I wonder if we can either hold it off until after Pyro has been
> released or make it possible to avoid it? The reason for this is that
> I know that this change wi
> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org
> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of
> Richard Purdie
> Sent: den 23 mars 2017 17:43
> To: Andre McCurdy; OE Core mailing list
> Subject: Re: [OE-core] U
On Wed, 2017-03-22 at 14:42 -0700, Andre McCurdy wrote:
> Currently native.bbclass clears MACHINEOVERRIDES but leaves
> MACHINE_FEATURES alone. Is that an oversight? Or is there ever a
> legitimate reason for a native recipe to have a dependency on
> MACHINE_FEATURES?
There is no good reason. Curr
On Wed, Mar 22, 2017 at 4:00 PM, Andre McCurdy wrote:
> On Wed, Mar 22, 2017 at 2:46 PM, Khem Raj wrote:
>> On Wed, Mar 22, 2017 at 2:42 PM, Andre McCurdy wrote:
>>> Currently native.bbclass clears MACHINEOVERRIDES but leaves
>>> MACHINE_FEATURES alone. Is that an oversight? Or is there ever a
>
On Wed, Mar 22, 2017 at 2:46 PM, Khem Raj wrote:
> On Wed, Mar 22, 2017 at 2:42 PM, Andre McCurdy wrote:
>> Currently native.bbclass clears MACHINEOVERRIDES but leaves
>> MACHINE_FEATURES alone. Is that an oversight? Or is there ever a
>> legitimate reason for a native recipe to have a dependency
On Wed, Mar 22, 2017 at 2:42 PM, Andre McCurdy wrote:
> Currently native.bbclass clears MACHINEOVERRIDES but leaves
> MACHINE_FEATURES alone. Is that an oversight? Or is there ever a
> legitimate reason for a native recipe to have a dependency on
> MACHINE_FEATURES?
MACHINE_FEATURES is specific t
