From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: [PATCH 0/4] sbuild-chroot optimizations
Date: Mon, 9 Jan 2023 06:32:31 +0100 [thread overview]
Message-ID: <cover.1673242355.git.jan.kiszka@siemens.com> (raw)
This primarily brings back pre-installed crosstools for sbuild-chroot, a
feature that was lost in the migration from buildchroot. It even
improves this further by adding two more dev packages and its deps so
that packages with minimal BuildDepends do not any need extra
installations.
Jan Kiszka (4):
sbuild-chroot: Only install ccache is used
crossbuild-essential-riscv64: Drop unneeded crossbuild disabling
sbuild-chroot: Pre-install cross-compiler and libc6-dev
sbuild-chroot: Pre-install also libcpp-*-dev and libstdc++-*-dev
meta-isar/conf/distro/raspios-bullseye.conf | 2 ++
meta-isar/conf/distro/ubuntu-focal.conf | 2 ++
meta/conf/distro/debian-bookworm.conf | 2 ++
meta/conf/distro/debian-bullseye.conf | 2 ++
meta/conf/distro/debian-buster.conf | 2 ++
.../crossbuild-essential-riscv64_0.2-isar.bb | 2 --
.../sbuild-chroot/sbuild-chroot-host.bb | 11 +++++++
.../sbuild-chroot/sbuild-chroot-target.bb | 4 +++
.../sbuild-chroot/sbuild-chroot.inc | 30 +++++++++++++++----
9 files changed, 50 insertions(+), 7 deletions(-)
--
2.35.3
next reply other threads:[~2023-01-09 5:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 5:32 Jan Kiszka [this message]
2023-01-09 5:32 ` [PATCH 1/4] sbuild-chroot: Only install ccache is used Jan Kiszka
2023-01-20 8:28 ` Jan Kiszka
2023-01-09 5:32 ` [PATCH 2/4] crossbuild-essential-riscv64: Drop unneeded crossbuild disabling Jan Kiszka
2023-01-09 5:32 ` [PATCH 3/4] sbuild-chroot: Pre-install cross-compiler and libc6-dev Jan Kiszka
2023-01-09 5:56 ` Moessbauer, Felix
2023-01-09 7:45 ` Jan Kiszka
2023-01-09 5:32 ` [PATCH 4/4] sbuild-chroot: Pre-install also libcpp-*-dev and libstdc++-*-dev Jan Kiszka
2023-01-24 7:33 ` [PATCH 0/4] sbuild-chroot optimizations Uladzimir Bely
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.1673242355.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.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