From: Alexander Kanavin <alex.kanavin@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Alexander Kanavin <alex@linutronix.de>
Subject: [PATCH 1/2] bitbake.conf: add an addfragments directive for oe-core and dependent layers
Date: Thu, 14 Nov 2024 12:10:59 +0100 [thread overview]
Message-ID: <20241114111100.2624737-1-alex.kanavin@gmail.com> (raw)
From: Alexander Kanavin <alex@linutronix.de>
Please see the patch to bitbake for syntax and implementation details.
The path prefix to fragments is in its own variable so it doesn't have
to be hardcoded into tools.
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
---
meta/conf/bitbake.conf | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 02bbf0e7a52..b6013f66e26 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -836,6 +836,8 @@ include conf/documentation.conf
include conf/licenses.conf
require conf/sanity.conf
include conf/bblock.conf
+OE_FRAGMENTS_PREFIX ?= "conf/fragments"
+addfragments ${OE_FRAGMENTS_PREFIX} OE_FRAGMENTS
##################################################################
# Weak variables (usually to retain backwards compatibility)
--
2.39.5
next reply other threads:[~2024-11-14 11:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 11:10 Alexander Kanavin [this message]
2024-11-14 11:11 ` [PATCH 2/2] bitbake-config-build: add a plugin for config fragments Alexander Kanavin
2024-11-14 11:16 ` Patchtest results for " patchtest
2024-11-14 13:20 ` [OE-core] " Mathieu Dubois-Briand
2024-11-14 13:33 ` Alexander Kanavin
2024-11-15 12:44 ` [OE-core] [PATCH 1/2] bitbake.conf: add an addfragments directive for oe-core and dependent layers Mathieu Dubois-Briand
2024-11-15 14:52 ` 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=20241114111100.2624737-1-alex.kanavin@gmail.com \
--to=alex.kanavin@gmail.com \
--cc=alex@linutronix.de \
--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