On Thu, Mar 23, 2017 at 12:09 PM, Patrick Ohly <patrick.o...@intel.com> wrote:
> On Thu, 2017-03-23 at 11:59 -0700, Andre McCurdy wrote:
>> On Thu, Mar 23, 2017 at 2:06 AM, Mike Looijmans <mike.looijm...@topic.nl>
>> wrote:
>> > On 22-03-17 23:47, Andre McCurdy wrote:
>> >>
>> >> Try to avoid native recipes accidentally being dependent on
>> >> MACHINE_FEATURES. This simple change doesn't prevent MACHINE_FEATURES
>> >> set via MACHINE_FEATURES_BACKFILL sneaking through, but it's better
>> >> than nothing.
>> >
>> > Maybe this would work:
>> >
>> > MACHINE_FEATURES_BACKFILL_CONSIDERED = "${MACHINE_FEATURES_BACKFILL}"
>>
>> I guess it doesn't work if MACHINE_FEATURES_BACKFILL_CONSIDERED is set
>> elsewhere using _append.
>>
>> The real solution would probably be to skip backfilling
>> MACHINE_FEATURES entirely for class-native?
>
> Perhaps set MACHINE_FEATURES_forcevariable = "" in native.bbclass?
Over-riding MACHINE_FEATURES doesn't work, presumably because the
ConfigParsed event handler which does the backfilling runs after
over-rides have been applied?
> --
> Best Regards, Patrick Ohly
>
> The content of this message is my personal opinion only and although
> I am an employee of Intel, the statements I make here in no way
> represent Intel's position on the issue, nor am I authorized to speak
> on behalf of Intel on this matter.
>
>
>
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
