If you do IMAGE_INSTALL_append in local.conf (or indeed CORE_IMAGE_EXTRA_INSTALL += or _append) to add something to an image, then run bitbake -c populate_sdk_ext imagename, you won't get those items in the SDK once installed. They do get built correctly, but because these variable changes aren't allowed through into the SDK's generated configuration, they aren't present at SDK installation time.
Hi Paul, How about just copying the contents of local.conf in TOPDIR into the final local.conf? The final local.conf looks like below. <start of local.conf> <contents from local.conf in TOPDIR> <contents generated which are specific for extensible SDK> <end of local.conf> In this way, other custom settings are also made into the final local.conf like DISTRO_FEATURES, VIRTUAL-RUNTIME_xxxx, etc. I think the only problem for the above approach is that some custom settings should not take effect in the final local.conf. SSTATE_DIR is absolutely one of them. I think we can make a blacklist, so that these variable don't get into the final local.conf. //Chen Qi
An update on status for everyone else's benefit: Qi is working on this - there have been a couple of rounds of review on the mailing list, hopefully the next version should be the final version.
Module: openembedded-core.git Branch: master Commit: 0dda443bfa5c42f327d8d0ed7b23af11c156a60e URL: http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=0dda443bfa5c42f327d8d0ed7b23af11c156a60e Author: Qi.Chen@windriver.com <Qi.Chen@windriver.com> Date: Mon Sep 7 13:42:23 2015 +0100
Verified with jethro:e1aa897beb33171bc902207b98c8f666b9e97ad3 Steps: 1. build the sdk and add mc to the SDK using INSTALL_IMAGE_append = " mc" in conf/local.conf 2. build the SDK: $ bitbake core-image-sato -c populate_sdk_ext 3. extract the sdk 4. in the new shell, source the extracted sdk env and build an image: $ devtool build-image core-image-sato 5. in a new shell, source a new poky to run the qemu image, log into it and search for mc: root@qemux86-64:~# which mc /usr/bin/mc