I think values for the BACKFILL_CONSIDERED can be used, but only if they are literals. I don't think any variable expansion occurs when getVar() is used at the point of backfilling. I think the a better way of setting MACHINE or DISTRO_FEATURES would be to directly append/remove using overrides. In any case, I do not believe any of the CONSIDERED definitions work.
Joe -----Original Message----- From: Andre McCurdy [mailto:[email protected]] Sent: Thursday, October 26, 2017 11:09 AM To: Slater, Joseph Cc: Alexander Kanavin; OE Core mailing list Subject: Re: [OE-core] [oe-core][PATCH 1/1] qemumips64: no qemu-usermode for n32 On Thu, Oct 26, 2017 at 10:15 AM, Slater, Joseph <[email protected]> wrote: > Okay, I don't know why, but at the time of backfilling the CONSIDERED list is > empty! This is not true if I use "=" to set it unconditionally in > arch-mips.inc, but it IS true if I try to set it via anything involving an > override (including append). > > Isn't getVar() supposed to expand the variable? Put print msg's in > meta/lib/oe/utils.py to see this behavior. features_backfill() is called from meta/classes/base.bbclass -> base_eventhandler() in response to bb.event.ConfigParsed (ie "when the base configuration; which consists of bitbake.conf, base.bbclass and any global INHERIT statements; has been parsed") so anything assigned to DISTRO_FEATURES_BACKFILL_CONSIDERED or MACHINE_FEATURES_BACKFILL_CONSIDERED after that event won't be seen... -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
