> -----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] Using MACHINE_FEATURES in a native recipe > > 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. Currently having this dilemma with > DISTRO_FEATURES too :/. > > opkg-native rebuilding if you enable/disable systemd isn't > expected/nice. > > Cheers, > > Richard
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 will require a huge amount of development work for us, something that will not be possible to do in the time frame left until Pyro is released. Or alternatively we will have to copy native.bbclass to our layers and maintain a fork of it, which sucks... The reason for this is that our unit test framework is based on building all our own packages as native, but still configured via, amongst others, MACHINE_FEATURES as if building for the real target. This will of course not work anymore if MACHINE_FEATURES is set to "" with no way of overriding it. //Peter -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
