From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: [PATCH] buildchroot: Drop build related packages
Date: Mon, 9 Jan 2023 12:44:28 +0100 [thread overview]
Message-ID: <0d5d8fa1-546a-0fbe-ba0b-4cad03ee788c@siemens.com> (raw)
From: Jan Kiszka <jan.kiszka@siemens.com>
We are no longer using buildchroot to build packages, only to run the
imager. Dropping everything apparently build-related saves both time and
space.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
Suggestions welcome if we can easily drop more.
Yes, there is the conversion series for the the imager which obsoletes
this. But my impression is that it will not be ready in the near future.
.../buildchroot/buildchroot-host.bb | 12 ------------
.../buildchroot/buildchroot-target.bb | 5 -----
meta/recipes-devtools/buildchroot/buildchroot.inc | 14 +-------------
3 files changed, 1 insertion(+), 30 deletions(-)
diff --git a/meta/recipes-devtools/buildchroot/buildchroot-host.bb b/meta/recipes-devtools/buildchroot/buildchroot-host.bb
index 529578d6..e5ce248e 100644
--- a/meta/recipes-devtools/buildchroot/buildchroot-host.bb
+++ b/meta/recipes-devtools/buildchroot/buildchroot-host.bb
@@ -11,15 +11,3 @@ require buildchroot.inc
ROOTFS_ARCH = "${HOST_ARCH}"
ROOTFS_DISTRO = "${HOST_DISTRO}"
ROOTFS_BASE_DISTRO = "${HOST_BASE_DISTRO}"
-
-BUILDCHROOT_PREINSTALL ?= " \
- ${BUILDCHROOT_PREINSTALL_COMMON} \
- libc6:${DISTRO_ARCH} \
- crossbuild-essential-${DISTRO_ARCH}"
-
-BUILDCHROOT_PREINSTALL_riscv64 ?= " \
- ${BUILDCHROOT_PREINSTALL_COMMON} \
- libc6:${DISTRO_ARCH} \
- gcc-riscv64-linux-gnu \
- g++-riscv64-linux-gnu \
- dpkg-cross"
diff --git a/meta/recipes-devtools/buildchroot/buildchroot-target.bb b/meta/recipes-devtools/buildchroot/buildchroot-target.bb
index be770449..6613de63 100644
--- a/meta/recipes-devtools/buildchroot/buildchroot-target.bb
+++ b/meta/recipes-devtools/buildchroot/buildchroot-target.bb
@@ -8,8 +8,3 @@ DESCRIPTION = "Isar development filesystem for target"
BUILDCHROOT_VARIANT = "target"
require buildchroot.inc
-
-BUILDCHROOT_PREINSTALL ?= " \
- ${BUILDCHROOT_PREINSTALL_COMMON} \
- gcc \
- build-essential"
diff --git a/meta/recipes-devtools/buildchroot/buildchroot.inc b/meta/recipes-devtools/buildchroot/buildchroot.inc
index c3067ad3..82fcfbf0 100644
--- a/meta/recipes-devtools/buildchroot/buildchroot.inc
+++ b/meta/recipes-devtools/buildchroot/buildchroot.inc
@@ -23,22 +23,10 @@ ROOTFS_MANIFEST_DEPLOY_DIR = "${DEPLOY_DIR_BUILDCHROOT}"
ROOTFS_DPKGSTATUS_DEPLOY_DIR = "${DEPLOY_DIR_BUILDCHROOT}"
ROOTFS_FEATURES += "generate-manifest export-dpkg-status"
-BUILDCHROOT_COMPAT_PREINSTALL_compat-arch = " \
- libc6:${COMPAT_DISTRO_ARCH} \
- crossbuild-essential-${COMPAT_DISTRO_ARCH}"
-
-BUILDCHROOT_PREINSTALL_COMMON = " \
- ${BUILDCHROOT_COMPAT_PREINSTALL} \
- make \
- debhelper \
- autotools-dev \
- ${@ 'ccache' if d.getVar('USE_CCACHE') == '1' else ''} \
+BUILDCHROOT_PREINSTALL ?= " \
dpkg \
locales \
- docbook-to-man \
apt \
- automake \
- devscripts \
equivs \
adduser"
--
2.35.3
next reply other threads:[~2023-01-09 11:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 11:44 Jan Kiszka [this message]
2023-01-25 7:17 ` 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=0d5d8fa1-546a-0fbe-ba0b-4cad03ee788c@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