from the manual:
OVERRIDES is a “:” separated variable containing each item you want to
satisfy conditions. So, if you have a variable which is conditional on
“arm”, and “arm” is in OVERRIDES, then the “arm” specific version of
the variable is used rather than the non-conditional version. Example:
OVERRIDES = "architecture:os:machine"
TEST = "defaultvalue"
TEST_os = "osspecificvalue"
TEST_condnotinoverrides = "othercondvalue"
In this example, TEST would be osspecificvalue, due to the condition
“os” being in OVERRIDES.
and what *would* happen if that second conditional variable was also
in OVERRIDES? would it override the first one? that should be
clarified here.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================_______________________________________________
Bitbake-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bitbake-dev
