From: Jan Kiszka <jan.kiszka@web.de>
To: Christopher Larson <kergoth@gmail.com>
Cc: isar-users <isar-users@googlegroups.com>,
Chao Zeng <chao.zeng@siemens.com>, Le Jin <le.jin@siemens.com>
Subject: Re: [PATCH 0/6] Evolve SDK to chroot-free usage
Date: Sat, 28 Mar 2020 08:33:45 +0100 [thread overview]
Message-ID: <e8805d3d-44b0-6d0f-be7a-fee4871e2f6b@web.de> (raw)
In-Reply-To: <CABcZANnu53G2g4D9hYO7=WMtQfjrB4-b17Fndn67KGVRM4Ne7g@mail.gmail.com>
On 28.03.20 00:48, Christopher Larson wrote:
> This series seems like a definite improvement, but I'd suggest
> explicitly noting in the README that once you've run the relocate-sdk.sh
> script, the second not recommended option of entering the chroot will no
> longer function due to the changed interpreter paths.
Correct. But we can enhance the relocation script so that it is also
able to restore the chroot mode. At least as long as we support both
modes, there is likely value in this. Will adjust it and the README.
Thanks,
Jan
>
> On Sun, Mar 22, 2020 at 1:37 AM Jan Kiszka <jan.kiszka@siemens.com
> <mailto:jan.kiszka@siemens.com>> wrote:
>
> Currently, our SDK can primarily be used by chroot'ing into it, taking
> the to-be-built project with you (bind mount etc.). This was enough for
> a start but we can do better.
>
> This series enhance the SDK to become usage as a normal cross-toolchain
> on your host system. For that purpose, we add a script that relocates
> the toolchain after installation, adjust binary search paths and
> sysroot. So, the only remaining difference to a yocto or buildroot
> toolchain is the need to run the relocation script once after unpacking
> the SDK.
>
> The series furthermore allows to customize the SDK content via the
> image-generating layer.
>
> The series (together with all other pending patching of mine) can also
> be found at https://github.com/siemens/isar/commits/jan/queue.
>
> While I already shrunk the SDK a bit by removing the now obsolete
> isar-apt repo, I suspect we could further reduce the deployment size by
> dropping chroot support completely, only including the compiler and
> their library dependencies. OTOH, sdk-debian-buster-arm64.tar.xz is now
> 142M here, unpacked 680M, while ARM's
> gcc-arm-8.3-2019.03-x86_64-aarch64-linux-gnu.tar.xz has
> 260M packed and 1.5G(!) unpacked. So we are either not really off or are
> still missing something.
>
> Jan
>
> Jan Kiszka (6):
> sdk: Add support for adding self-defined sdk packages
> sdk: Make all links in the SDK chroot relative
> sdk: Add script to relocate SDK
> sdk: Do not ship the isar-apt repo
> sdk: Inject sysroot path when calling relocated toolchain
> sdk: Update README.sdk
>
> doc/user_manual.md | 1 +
> meta/classes/image-sdk-extension.bbclass | 28 ++++++++-
> meta/recipes-devtools/sdkchroot/files/README.sdk | 66
> ++++++++++------------
> .../sdkchroot/files/relocate-sdk.sh | 32 +++++++++++
> meta/recipes-devtools/sdkchroot/sdkchroot.bb
> <http://sdkchroot.bb> | 35 ++++++------
> 5 files changed, 108 insertions(+), 54 deletions(-)
> create mode 100755
> meta/recipes-devtools/sdkchroot/files/relocate-sdk.sh
>
> --
> 2.16.4
>
> --
> You received this message because you are subscribed to the Google
> Groups "isar-users" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to isar-users+unsubscribe@googlegroups.com
> <mailto:isar-users%2Bunsubscribe@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/isar-users/cover.1584866240.git.jan.kiszka%40siemens.com.
>
>
>
> --
> Christopher Larson
> kergoth at gmail dot com
> Founder - BitBake, OpenEmbedded, OpenZaurus
> Senior Software Engineer, Mentor Graphics
prev parent reply other threads:[~2020-03-28 7:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-22 8:37 Jan Kiszka
2020-03-22 8:37 ` [PATCH 1/6] sdk: Add support for adding self-defined sdk packages Jan Kiszka
2020-03-22 8:37 ` [PATCH 2/6] sdk: Make all links in the SDK chroot relative Jan Kiszka
2020-03-22 8:37 ` [PATCH 3/6] sdk: Add script to relocate SDK Jan Kiszka
2020-03-22 8:37 ` [PATCH 4/6] sdk: Do not ship the isar-apt repo Jan Kiszka
2020-03-22 8:37 ` [PATCH 5/6] sdk: Inject sysroot path when calling relocated toolchain Jan Kiszka
2020-03-22 8:55 ` [PATCH v2 " Jan Kiszka
2020-03-22 8:37 ` [PATCH 6/6] sdk: Update README.sdk Jan Kiszka
2020-03-27 23:48 ` [PATCH 0/6] Evolve SDK to chroot-free usage Christopher Larson
2020-03-28 7:33 ` Jan Kiszka [this message]
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=e8805d3d-44b0-6d0f-be7a-fee4871e2f6b@web.de \
--to=jan.kiszka@web.de \
--cc=chao.zeng@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=kergoth@gmail.com \
--cc=le.jin@siemens.com \
/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