We need to examine what sstate artifacts we need to go into constructing the SDK when it contains the build system; if we simply use task dependencies as set up at the moment just to be able to build core-image-minimal we end up with something that is ~1.5GB compressed (i.e. composed of the host part of the SDK + metadata + sstate artifacts). We should try to reduce this if at all possible. (This may also be about deciding how we specify the SDK capabilities / contents, so that the user can tailor the SDK to their requirements.)
Clarification - this applies to the extensible SDK (bitbake -c populate_sdk_ext)
There are a few different configurations I can think of: 1) The current mode, where you get all of the artifacts required to do a build against something in the image 2) "Light" mode where you get do_populate_sysroot executed for the toolchain and all of the recipes for the packages in the image 3) Maybe a "super-light" mode where you get just the toolchain? (we probably want better switch naming than "light" / "super-light" etc.) With all of these we have the option of having SSTATE_MIRRORS set so that sstate archives can be pulled in from a server as needed, at least for building images and packages that will work automatically. Note: during ext SDK construction if we know we aren't including the full sstate for the image and SSTATE_MIRRORS isn't set in the local.conf file we've created, we should configure devtool to hide or disable the build-image and package subcommands since they won't be usable.
I've split off that last paragraph to a new bug - bug 8789 - so that this one can be dedicated to just providing the means to cut down the size of the extensible SDK.
Should be fixed with commit 4f7656a2047f4f67c3965693c3ca9f94e634cd9d Author: Randy Witt <randy.e.witt@linux.intel.com> Date: Thu Feb 4 12:31:44 2016 -0800 https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=4f7656a2047f4f67c3965693c3ca9f94e634cd9d