On Wed, Jun 13, 2018 at 03:58:27PM +0200, Maxim Yu. Osipov wrote:
> --- a/meta/classes/image.bbclass
> +++ b/meta/classes/image.bbclass
> @@ -71,3 +71,11 @@ do_copy_boot_files() {
>  addtask copy_boot_files before do_build after do_rootfs
>  do_copy_boot_files[dirs] = "${DEPLOY_DIR_IMAGE}"
>  do_copy_boot_files[stamp-extra-info] = "${DISTRO}-${MACHINE}"
> +
> +do_isar_sdk() {
> +}
> +
> +do_isar_sdk[stamp-extra-info] = "${MACHINE}-${DISTRO}"
> +do_isar_sdk[depends] = "sdkchroot:do_build"

Yocto SDK is generated as follows [1]:

bitbake -c populate_sdk core-image-base

or in the older way [2]:

bitbake meta-toolchain

The latter doesn't include local target stuff like libhello-dev in the sysroot.

The SDK is provided as a self-extracting script under build/tmp/deploy/sdk
(e.g., product-glibc-i686-meta-toolchain-armhf-toolchain-2.0.sh). Executed with
a directory as an argument, it extracts the files there. In the directory,
there is an environment setup script (e.g.,
environment-setup-armhf-product-linux) that sets the vars used for building
(attached).

We could use populate_sdk and meta-toolchain as user-visible task and recipe
names (keeping the sdkchroot directory name to follow buildchroot and
buildchroot-cross). Advantages:

* Pick up developers familiar with Yocto.

* UX harmonization with Deby and ELBE using poky as base layer.

Disadvantages:

* People coming from Yocto might be surprised to find a chroot tarball instead
  of a self-extractor and environment setup script.

What do you think?


Possible future extensions:

* Generate environment-setup for using without chrooting.

* Generate complete VM images for specific virtualization environments.

That would eliminate the sudo requirement for users.


References:

1. https://www.yoctoproject.org/docs/2.5/adt-manual/adt-manual.html#sdk-building-an-sdk-installer
2. https://www.yoctoproject.org/docs/1.6.1/adt-manual/adt-manual.html#optionally-building-a-toolchain-installer


With kind regards,
Baurzhan.