From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH v3 4/5] buildstats: Enable buildstats in default configuration
Date: Fri, 19 Nov 2021 10:24:58 +0100 [thread overview]
Message-ID: <20211119092459.27376-5-ubely@ilbers.de> (raw)
In-Reply-To: <20211119092459.27376-1-ubely@ilbers.de>
Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
---
meta-isar/conf/local.conf.sample | 3 +++
meta/conf/bitbake.conf | 1 +
2 files changed, 4 insertions(+)
diff --git a/meta-isar/conf/local.conf.sample b/meta-isar/conf/local.conf.sample
index 42a69aed..85c2ea10 100644
--- a/meta-isar/conf/local.conf.sample
+++ b/meta-isar/conf/local.conf.sample
@@ -225,6 +225,9 @@ USER_isar[flags] = "system create-home"
USER_isar[password] = "isar"
USER_isar[flags] += "clear-text-password"
+# Use buildstats by default
+USE_BUILDSTATS = "1"
+
# Uncomment the below line to debug WIC.
# WIC_CREATE_EXTRA_ARGS += "-D"
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index f056ad19..b47e6de7 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -117,6 +117,7 @@ INHERIT += "isar-events"
# Buildstats requires IMAGE_ROOTFS to be always defined
IMAGE_ROOTFS ??= "${WORKDIR}/rootfs"
+INHERIT += "${@'buildstats' if d.getVar('USE_BUILDSTATS') == '1' else ''}"
# Default values for ccache
USE_CCACHE ??= "0"
--
2.20.1
next prev parent reply other threads:[~2021-11-19 9:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 9:24 [PATCH v3 0/5] Use buildstats from OE to generate build charts Uladzimir Bely
2021-11-19 9:24 ` [PATCH v3 1/5] oe imports in central location Uladzimir Bely
2021-11-19 9:24 ` [PATCH v3 2/5] buildstats: Borrow buildstats and pybootchartgui from OE Uladzimir Bely
2021-11-19 9:24 ` [PATCH v3 3/5] buildstats: Fixes to work with bbclass in ISAR Uladzimir Bely
2021-11-19 9:24 ` Uladzimir Bely [this message]
2021-11-19 9:24 ` [PATCH v3 5/5] doc: Add buildstats section in user manual Uladzimir Bely
2021-12-01 13:24 ` [PATCH v3 0/5] Use buildstats from OE to generate build charts 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=20211119092459.27376-5-ubely@ilbers.de \
--to=ubely@ilbers.de \
--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