From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH] bitbake.conf,lib/configfragments: Use a new dedicated toolcfg.conf file
Date: Mon, 6 Oct 2025 14:21:12 +0100 [thread overview]
Message-ID: <20251006132112.847125-1-richard.purdie@linuxfoundation.org> (raw)
Rather than using auto.conf which already has established use in CI, or
local.conf which users expect to own/control, start writing "tooling"
controlled settings to a toolcfg.conf.
This frees CI to handle auto.conf as it wants, but avoids the tooling
breaking users local.conf files.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
meta/conf/bitbake.conf | 1 +
meta/lib/bbconfigbuild/configfragments.py | 4 ++--
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index eebefc48406..8d1ea5491de 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -813,6 +813,7 @@ FILESOVERRIDES = "${TRANSLATED_TARGET_ARCH}:${MACHINEOVERRIDES}:${DISTROOVERRIDE
require conf/abi_version.conf
include conf/site.conf
include conf/auto.conf
+include conf/toolcfg.conf
include conf/local.conf
OE_FRAGMENTS_PREFIX ?= "conf/fragments"
diff --git a/meta/lib/bbconfigbuild/configfragments.py b/meta/lib/bbconfigbuild/configfragments.py
index 34c6a3b4bcc..21baedc9a42 100644
--- a/meta/lib/bbconfigbuild/configfragments.py
+++ b/meta/lib/bbconfigbuild/configfragments.py
@@ -115,7 +115,7 @@ class ConfigFragmentsPlugin(LayerPlugin):
def create_conf(self, confpath):
if not os.path.exists(confpath):
with open(confpath, 'w') as f:
- f.write('')
+ f.write('# Automated config file controlled by tools\n')
with open(confpath, 'r') as f:
lines = f.read()
if "OE_FRAGMENTS += " not in lines:
@@ -184,7 +184,7 @@ class ConfigFragmentsPlugin(LayerPlugin):
print("All fragments removed from {}.".format(args.confpath))
def register_commands(self, sp):
- default_confpath = os.path.join(os.environ["BBPATH"], "conf/auto.conf")
+ default_confpath = os.path.join(os.environ["BBPATH"], "conf/toolcfg.conf")
parser_list_fragments = self.add_command(sp, 'list-fragments', self.do_list_fragments, parserecipes=False)
parser_list_fragments.add_argument("--confpath", default=default_confpath, help='Configuration file which contains a list of enabled fragments (default is {}).'.format(default_confpath))
next reply other threads:[~2025-10-06 13:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 13:21 Richard Purdie [this message]
2025-10-06 13:48 ` [OE-core] [PATCH] bitbake.conf,lib/configfragments: Use a new dedicated toolcfg.conf file Alexander Kanavin
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=20251006132112.847125-1-richard.purdie@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
/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