Re: [PATCH] sdk: Move deployment to populate_sdk

[Jan Kiszka <jan.kiszka@siemens.com>]

On 2018-08-28 11:46, Maxim Yu. Osipov wrote:
> Deploy SDK after Isar packages get deployed to
> local Isar apt repo which is copied afterwards
> to sdkchroot.
> 
> Signed-off-by: Maxim Yu. Osipov <mosipov@ilbers.de>
> ---
>   meta/classes/image.bbclass                   | 11 +++++++++++
>   meta/recipes-devtools/sdkchroot/sdkchroot.bb |  8 --------
>   2 files changed, 11 insertions(+), 8 deletions(-)
> 
> diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
> index 6a5f0e9..30f8eaa 100644
> --- a/meta/classes/image.bbclass
> +++ b/meta/classes/image.bbclass
> @@ -97,7 +97,18 @@ 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}"
>   
> +SDKCHROOT_DIR = "${TMPDIR}/work/${DISTRO}-${DISTRO_ARCH}/sdkchroot-${HOST_DISTRO}-${HOST_ARCH}"
> +
>   do_populate_sdk() {
> +    # Copy isar-apt with deployed Isar packages
> +    sudo cp -Trpfx ${DEPLOY_DIR_APT}/${HOST_DISTRO}  ${SDKCHROOT_DIR}/rootfs/isar-apt

That also creates the general SDK question: What's the deal with 
${DEPLOY_DIR_APT}/${HOST_DISTRO} vs. ${DEPLOY_DIR_APT}/${DISTRO}. May 
both contain packages? Where do locally built packages go to, in native 
as well as cross mode? /me still confused.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux