From: Henning Schild <henning.schild@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>
Cc: <isar-users@googlegroups.com>
Subject: Re: [PATCH 2/3] classes/image: Add mount_chroot.sh script to the final sdk image
Date: Thu, 21 Feb 2019 18:38:02 +0100 [thread overview]
Message-ID: <20190221183802.0164014f@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20190220194355.24046-3-mosipov@ilbers.de>
That reminds me that we really need a task like "devshell" that gives
you an interactive shell in the fully mounted/qemued buildchroot to
resolve the complicated issues.
Henning
Am Wed, 20 Feb 2019 20:43:54 +0100
schrieb "Maxim Yu. Osipov" <mosipov@ilbers.de>:
> Suggested-by: Jan Kiszka <jan.kiszka@siemens.com>
> Signed-off-by: Maxim Yu. Osipov <mosipov@ilbers.de>
> ---
> meta/classes/image.bbclass | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
> index d15d946..2514c88 100644
> --- a/meta/classes/image.bbclass
> +++ b/meta/classes/image.bbclass
> @@ -148,6 +148,9 @@ do_populate_sdk() {
> # Remove setup scripts
> sudo rm -f ${SDKCHROOT_DIR}/rootfs/chroot-setup.sh
> ${SDKCHROOT_DIR}/rootfs/configscript.sh
> + # Copy mount_chroot.sh for convenience
> + sudo cp ${ISARROOT}/scripts/mount_chroot.sh
> ${SDKCHROOT_DIR}/rootfs +
> # Create SDK archive
> sudo tar -C ${SDKCHROOT_DIR}
> --transform="s|^rootfs|sdk-${DISTRO}-${DISTRO_ARCH}|" \ -c rootfs |
> xz -T0 > ${DEPLOY_DIR_IMAGE}/sdk-${DISTRO}-${DISTRO_ARCH}.tar.xz
next prev parent reply other threads:[~2019-02-21 17:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 19:43 [PATCH 0/3] Improve SDK packaging Maxim Yu. Osipov
2019-02-20 19:43 ` [PATCH 1/3] classes/image: Remove setup scripts from final sdk image Maxim Yu. Osipov
2019-02-20 19:43 ` [PATCH 2/3] classes/image: Add mount_chroot.sh script to the " Maxim Yu. Osipov
2019-02-21 17:38 ` Henning Schild [this message]
2019-02-20 19:43 ` [PATCH 3/3] sdk: Provide README inside sdkchroot Maxim Yu. Osipov
2019-02-27 9:35 ` [PATCH 0/3] Improve SDK packaging Maxim Yu. Osipov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190221183802.0164014f@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=mosipov@ilbers.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox