path: root/meta/recipes-core/meta/
diff options
authorRandy Witt <>2015-02-23 17:00:43 +0000
committerRichard Purdie <>2015-02-23 18:00:12 +0000
commitbf81d6bb7f6df5405b8f2148e2a22e0030c12757 (patch)
tree4245294163f94df7e0ac94ca7dde60dec2690fee /meta/recipes-core/meta/
parent6d847b84b9db2b315e17107a7ab4832d15cb2147 (diff)
populate_sdk_ext: add extensible SDK
This bbclass will create an SDK with a copy of bitbake and the metadata and sstate for the target specified for the task. The idea is to let "system" developers both work on applications and then test adding them to an image without having to switch between workspaces or having to download separate items. Rather than running bitbake directly however, the primary way of running builds within the extensible SDK is to use the "devtool" command. The rest of the build system is fixed via locked shared state signatures, and thus only the recipes you have added get built. Signed-off-by: Paul Eggleton <> Signed-off-by: Randy Witt <> Signed-off-by: Chen Qi <> Signed-off-by: Richard Purdie <>
Diffstat (limited to 'meta/recipes-core/meta/')
1 files changed, 12 insertions, 0 deletions
diff --git a/meta/recipes-core/meta/ b/meta/recipes-core/meta/
new file mode 100644
index 0000000000..d9e596143f
--- /dev/null
+++ b/meta/recipes-core/meta/
@@ -0,0 +1,12 @@
+# meta-environment for extensible SDK
+PN = "meta-environment-extsdk-${MACHINE}"
+create_sdk_files_append() {
+ local sysroot=${SDKPATH}/${@os.path.relpath(d.getVar('STAGING_DIR_TARGET', True), d.getVar('TOPDIR', True))}
+ local sdkpathnative=${SDKPATH}/${@os.path.relpath(d.getVar('STAGING_DIR_NATIVE',True), d.getVar('TOPDIR', True))}
+ toolchain_create_sdk_env_script '' '' $sysroot '' ${bindir_native} ${prefix_native} $sdkpathnative