diff options
author | Paul Eggleton <paul.eggleton@linux.intel.com> | 2016-03-31 21:53:31 +1300 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-03-31 23:01:36 +0100 |
commit | 591b97c6bee1bf25ba44309923059c6aa9a624bd (patch) | |
tree | 6ffdbc3ec5f86012eb1add1a9d3e96271fba31bc /scripts/contrib/list-packageconfig-flags.py | |
parent | c37d5426b1872d29347c1fecd9bda7b455fa15e0 (diff) | |
download | poky-591b97c6bee1bf25ba44309923059c6aa9a624bd.tar.gz |
classes/populate_sdk_ext: support setting vars from environment at build time
When running bitbake you may pass in values of variables from the
external environment (making use of BB_ENV_EXTRAWHITE), and you may
choose to do this when building the extensible SDK, for example:
MACHINE=qemuarm bitbake -c populate_sdk_ext core-image-minimal
You would naturally expect those settings to be reflected in the
extensible SDK itself; however they were not, since we were only
considering local.conf and auto.conf. Check the variables mentioned in
BB_ENV_EXTRAWHITE to see if any are different than the values set in
local.conf/auto.conf and add lines setting them in the SDK's local.conf
if so.
Fixes [YOCTO #9339].
(From OE-Core rev: 2bfed75c48a6f6596ded9cb64cb96f00510f914e)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'scripts/contrib/list-packageconfig-flags.py')
0 files changed, 0 insertions, 0 deletions