summaryrefslogtreecommitdiffstats
path: root/meta/recipes-connectivity/bluez5
diff options
context:
space:
mode:
authorPaul Eggleton <paul.eggleton@linux.intel.com>2017-04-19 20:57:28 +1200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2017-04-19 10:38:37 +0100
commit9e267ad1739d460127e4c7ab71e886e0b1f153a1 (patch)
tree84170a37821949a5f94b3a10c165a8859df7a172 /meta/recipes-connectivity/bluez5
parent6ffec971e8e01964c4393c54872400d489a5c0d6 (diff)
downloadpoky-9e267ad1739d460127e4c7ab71e886e0b1f153a1.tar.gz
classes/populate_sdk_ext: work around runqemu behaviour within the eSDK
Currently, in order to figure out variable values when run within the eSDK, runqemu does not use the standard SDK method nor is it able to run bitbake (since the eSDK environment isn't initialised like the normal OE build environment). runqemu really ought to be fixed, but the quick workaround is to set DEPLOY_DIR_IMAGE in the environment so that runqemu can find image files. Fixes [YOCTO #10447]. (From OE-Core rev: 1ef833b6393366a10f4bb65df89725ad65761386) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-connectivity/bluez5')
0 files changed, 0 insertions, 0 deletions