From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Cc: Chao Zeng <chao.zeng@siemens.com>, Le Jin <le.jin@siemens.com>
Subject: [PATCH 0/6] Evolve SDK to chroot-free usage
Date: Sun, 22 Mar 2020 09:37:15 +0100 [thread overview]
Message-ID: <cover.1584866240.git.jan.kiszka@siemens.com> (raw)
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 | 35 ++++++------
5 files changed, 108 insertions(+), 54 deletions(-)
create mode 100755 meta/recipes-devtools/sdkchroot/files/relocate-sdk.sh
--
2.16.4
next reply other threads:[~2020-03-22 8:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-22 8:37 Jan Kiszka [this message]
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
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=cover.1584866240.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=chao.zeng@siemens.com \
--cc=isar-users@googlegroups.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