From: Florian Bezdeka <florian.bezdeka@siemens.com>
To: isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com, Florian Bezdeka <florian.bezdeka@siemens.com>
Subject: [PATCH] buildchroot: Install ccache into the buildchroot only when enabled
Date: Fri, 10 Jun 2022 18:28:31 +0200 [thread overview]
Message-ID: <20220610162831.704538-1-florian.bezdeka@siemens.com> (raw)
This fixes a corner case where the buildchroot is not directly fetched
from Debian upstream repos but from something like a (manually
maintained) snapshot. There is no guarantee that the ccache packet is
available inside the buildchroot packet feed.
As soon as ccache is enabled by setting "USE_CCACHE" to "1" the packet
will be installed into the buildchroot.
Fixes: 20a2ff7704a2 ("meta: Support for ccache for custom packages")
Signed-off-by: Florian Bezdeka <florian.bezdeka@siemens.com>
---
meta/recipes-devtools/buildchroot/buildchroot.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/buildchroot/buildchroot.inc b/meta/recipes-devtools/buildchroot/buildchroot.inc
index aa190e9..c3067ad 100644
--- a/meta/recipes-devtools/buildchroot/buildchroot.inc
+++ b/meta/recipes-devtools/buildchroot/buildchroot.inc
@@ -32,7 +32,7 @@ BUILDCHROOT_PREINSTALL_COMMON = " \
make \
debhelper \
autotools-dev \
- ccache \
+ ${@ 'ccache' if d.getVar('USE_CCACHE') == '1' else ''} \
dpkg \
locales \
docbook-to-man \
--
2.35.3
next reply other threads:[~2022-06-10 16:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 16:28 Florian Bezdeka [this message]
2022-06-13 7:13 ` Jan Kiszka
2022-06-23 18:04 ` Anton Mikanovich
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=20220610162831.704538-1-florian.bezdeka@siemens.com \
--to=florian.bezdeka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@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