aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPaul Eggleton <paul.eggleton@linux.intel.com>2017-04-19 20:38:46 +1200
committerPaul Eggleton <paul.eggleton@linux.intel.com>2017-04-19 20:56:26 +1200
commit55fe27e1f64352d36e4a49eb488a51bda21bd007 (patch)
tree5a0a915fbaa10d3a6036358700b0bc60a1d931a3
parent63ad928771459b7087ce69f5f372d159c02103f9 (diff)
downloadopenembedded-core-contrib-55fe27e1f64352d36e4a49eb488a51bda21bd007.tar.gz
openembedded-core-contrib-55fe27e1f64352d36e4a49eb488a51bda21bd007.tar.bz2
openembedded-core-contrib-55fe27e1f64352d36e4a49eb488a51bda21bd007.zip
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]. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
-rw-r--r--meta/classes/populate_sdk_ext.bbclass2
1 files changed, 2 insertions, 0 deletions
diff --git a/meta/classes/populate_sdk_ext.bbclass b/meta/classes/populate_sdk_ext.bbclass
index 3e1858c0319..4dfb94caf16 100644
--- a/meta/classes/populate_sdk_ext.bbclass
+++ b/meta/classes/populate_sdk_ext.bbclass
@@ -577,6 +577,8 @@ sdk_ext_postinst() {
# Allow bitbake environment setup to be ran as part of this sdk.
echo "export OE_SKIP_SDK_CHECK=1" >> $env_setup_script
+ # Work around runqemu not knowing how to get this information within the eSDK
+ echo "export DEPLOY_DIR_IMAGE=$target_sdk_dir/tmp/${@os.path.relpath(d.getVar('DEPLOY_DIR_IMAGE'), d.getVar('TMPDIR'))}" >> $env_setup_script
# A bit of another hack, but we need this in the path only for devtool
# so put it at the end of $PATH.