From: Alexander Kanavin <alex.kanavin@gmail.com>
To: poky@lists.yoctoproject.org
Cc: Alexander Kanavin <alex@linutronix.de>
Subject: [PATCH 2/2] meta-poky/conf/templates: add a blank template
Date: Mon, 23 Jun 2025 18:55:07 +0200 [thread overview]
Message-ID: <20250623165507.1633860-2-alex.kanavin@gmail.com> (raw)
In-Reply-To: <20250623165507.1633860-1-alex.kanavin@gmail.com>
From: Alexander Kanavin <alex@linutronix.de>
The default oe-core/poky templates have a number of settings
(such as distro and machine) and are thus unsuitable for
building up configurations from fragments. This adds a template
with an empty local.conf, so that it can be used as the starting
point for fragment-driven configuration.
There will also be a blank template in oe-core; the difference is
that this one includes poky layers and the oe-core one does not.
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
---
.../conf/templates/blank/bblayers.conf.sample | 12 ++++++++++++
meta-poky/conf/templates/blank/conf-notes.txt | 19 +++++++++++++++++++
.../conf/templates/blank/conf-summary.txt | 1 +
.../conf/templates/blank/local.conf.sample | 10 ++++++++++
4 files changed, 42 insertions(+)
create mode 100644 meta-poky/conf/templates/blank/bblayers.conf.sample
create mode 100644 meta-poky/conf/templates/blank/conf-notes.txt
create mode 100644 meta-poky/conf/templates/blank/conf-summary.txt
create mode 100644 meta-poky/conf/templates/blank/local.conf.sample
diff --git a/meta-poky/conf/templates/blank/bblayers.conf.sample b/meta-poky/conf/templates/blank/bblayers.conf.sample
new file mode 100644
index 00000000000..d34b552cb71
--- /dev/null
+++ b/meta-poky/conf/templates/blank/bblayers.conf.sample
@@ -0,0 +1,12 @@
+# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf
+# changes incompatibly
+POKY_BBLAYERS_CONF_VERSION = "2"
+
+BBPATH = "${TOPDIR}"
+BBFILES ?= ""
+
+BBLAYERS ?= " \
+ ##OEROOT##/meta \
+ ##OEROOT##/../meta-yocto/meta-poky \
+ ##OEROOT##/../meta-yocto/meta-yocto-bsp \
+ "
diff --git a/meta-poky/conf/templates/blank/conf-notes.txt b/meta-poky/conf/templates/blank/conf-notes.txt
new file mode 100644
index 00000000000..cfd1f1977bf
--- /dev/null
+++ b/meta-poky/conf/templates/blank/conf-notes.txt
@@ -0,0 +1,19 @@
+
+### Shell environment set up for builds. ###
+
+You can now run 'bitbake <target>'
+
+Common targets are:
+ core-image-minimal
+ core-image-full-cmdline
+ core-image-sato
+ core-image-weston
+ meta-toolchain
+ meta-ide-support
+
+You can also run generated qemu images with a command like 'runqemu qemux86-64'.
+
+Other commonly useful commands are:
+ - 'devtool' and 'recipetool' handle common recipe tasks
+ - 'bitbake-layers' handles common layer tasks
+ - 'oe-pkgdata-util' handles common target package tasks
diff --git a/meta-poky/conf/templates/blank/conf-summary.txt b/meta-poky/conf/templates/blank/conf-summary.txt
new file mode 100644
index 00000000000..7528c297947
--- /dev/null
+++ b/meta-poky/conf/templates/blank/conf-summary.txt
@@ -0,0 +1 @@
+This configuration is empty and is intended as a starting point for adding configuration fragments.
diff --git a/meta-poky/conf/templates/blank/local.conf.sample b/meta-poky/conf/templates/blank/local.conf.sample
new file mode 100644
index 00000000000..41eea8506df
--- /dev/null
+++ b/meta-poky/conf/templates/blank/local.conf.sample
@@ -0,0 +1,10 @@
+#
+# This file is intended for local configuration tweaks. It is intentionally
+# set up empty, so that configuration can be constructed from fragments
+# using bitbake-config-build tool and by setting MACHINE and DISTRO here.
+#
+# If you would like to publish this file (for example as a bitbake
+# configuration template), it is recommended to create fragments
+# from changes made here; the only settings that can remain are
+# MACHINE and DISTRO.
+#
--
2.39.5
next prev parent reply other threads:[~2025-06-23 16:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 16:55 [PATCH 1/2] meta-poky/conf/templates/default/bblayers.conf.sample: do not assume integrated poky repo Alexander Kanavin
2025-06-23 16:55 ` Alexander Kanavin [this message]
2025-06-24 13:11 ` [poky] " Richard Purdie
2025-06-24 13:42 ` Alexander Kanavin
2025-06-24 13:58 ` Richard Purdie
2025-06-24 14:02 ` Alexander Kanavin
2025-06-24 16:00 ` Alexander Kanavin
[not found] ` <184C05EBFBF7A622.2779@lists.yoctoproject.org>
2025-06-25 13:56 ` Alexander Kanavin
[not found] ` <184C4DB835DB2097.24592@lists.yoctoproject.org>
2025-06-30 10:21 ` [yocto] " 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=20250623165507.1633860-2-alex.kanavin@gmail.com \
--to=alex.kanavin@gmail.com \
--cc=alex@linutronix.de \
--cc=poky@lists.yoctoproject.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