<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/bitbake/bin/bitbake-setup, branch master-next</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=master-next</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=master-next'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2025-11-07T10:20:32+00:00</updated>
<entry>
<title>bitbake: bitbake-setup: Rename bb-layers-relative to bb-layers-file-relative</title>
<updated>2025-11-07T10:20:32+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2025-11-07T08:00:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=2aeb91cdb370197dfbb7b14afb0bdd96538c9dc1'/>
<id>urn:sha1:2aeb91cdb370197dfbb7b14afb0bdd96538c9dc1</id>
<content type='text'>
The difference between bb-layers and bb-layers-relative is unclear as both
are relative paths. Rename one to "file-relative" which makes it clear it
is relative to the current file, without becomming a long name.

https://lists.openembedded.org/g/bitbake-devel/message/18296

Based on a patch from Alexander Kanavin &lt;alex@linutronix.de&gt; but
with different naming.

(Bitbake rev: dcb17758b99767ab6da4172cf60eabc9269082dd)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: bitbake-setup: replace {THISDIR} token with a keyword: bb-layers-relative</title>
<updated>2025-11-06T18:04:13+00:00</updated>
<author>
<name>Alexander Kanavin</name>
<email>alex@linutronix.de</email>
</author>
<published>2025-11-06T17:08:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=516039e60916da4c3bb39f0d0c18d721e7ecf75e'/>
<id>urn:sha1:516039e60916da4c3bb39f0d0c18d721e7ecf75e</id>
<content type='text'>
{THISDIR} is a special value token that can be used in the list of enabled
layers to specify the layer location relative to the confguration file:
https://git.openembedded.org/bitbake/commit/?id=b3153be29de8b8570b0c184369bd41f4c646cf92

This replaces the token with an explicit separate keyword for such layers:
so that special processing to determine the final value can be avoided, and
the feature can be formalized in the json schema:

instead of
   "bb-layers": [
        "{THISDIR}/meta-my-project"
    ]

this allows
   "bb-layers-relative": [
        "meta-my-project"

Going forward I think we should strive to avoid any further special value tokens.

(Bitbake rev: 90da82bd2bfcfd5590c9ae06015737b616074b56)

Signed-off-by: Alexander Kanavin &lt;alex@linutronix.de&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: bitbake-setup: capture revisions while checking out layers</title>
<updated>2025-11-06T18:03:46+00:00</updated>
<author>
<name>Johannes Schneider</name>
<email>johannes.schneider@leica-geosystems.com</email>
</author>
<published>2025-11-05T19:06:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=9780ec24d070b0638492c0f153a7ed776c150ed5'/>
<id>urn:sha1:9780ec24d070b0638492c0f153a7ed776c150ed5</id>
<content type='text'>
When initializing a build setup from a conf.json that only sets 'rev'
to a tag or branch, the actual revision would not be captured or
logged.

To capture the current layer state after an 'init' or 'update', the
checkout_layers function is extended to store the revision the
bb.fetch.Fetch pulled, and write that information into a
sources-fixed-revisions.json file. This file can then be fed back into
bitbake-setup init as: --sources-overrides

This new 'sources-fixed-revisions.json' is written during 'update_build' and
stored alongside the 'config-upstream.json' in the config dir. And put
with the later under version control by calling 'commit_config" after
'update_build'.

The use of 'deepcopy' is necessary to not modify the original input
data - which python passes around as reference.

(Bitbake rev: 95866ff03f78e987ae7e47daad053bc0f353eea4)

Signed-off-by: Johannes Schneider &lt;johannes.schneider@leica-geosystems.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: bitbake-setup: checkout_layers: construct 'src_uri' separatly</title>
<updated>2025-11-06T18:03:46+00:00</updated>
<author>
<name>Johannes Schneider</name>
<email>johannes.schneider@leica-geosystems.com</email>
</author>
<published>2025-11-05T19:06:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=5de850ec0148e576a4f1e5cdfa813d65a5016b86'/>
<id>urn:sha1:5de850ec0148e576a4f1e5cdfa813d65a5016b86</id>
<content type='text'>
Construct the 'src_uri' separately, and then pass either variant into
one call that creates the Fetch. Making use of format-strings to
shorten/simplify the code.

Also: using 'proto' instead of 'type' for a variable name, to avoid
the protected keyword.

(Bitbake rev: 4ad70e05ceca19c1e903dafc33386a82b1176bba)

Signed-off-by: Johannes Schneider &lt;johannes.schneider@leica-geosystems.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: bitbake-setup: rename 'write_config' into 'write_upstream_config'</title>
<updated>2025-11-06T18:03:46+00:00</updated>
<author>
<name>Johannes Schneider</name>
<email>johannes.schneider@leica-geosystems.com</email>
</author>
<published>2025-11-05T19:06:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=729e6f2cfda4cb1aefc7c6d03b6f834138fb1ed8'/>
<id>urn:sha1:729e6f2cfda4cb1aefc7c6d03b6f834138fb1ed8</id>
<content type='text'>
Rename the function to reflect which (of the possibly many) files in
the build/config directory it writes to.

(Bitbake rev: 7f9cd4c1e91d110085d74f9b9f12884f97f4e8dd)

Signed-off-by: Johannes Schneider &lt;johannes.schneider@leica-geosystems.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: bitbake-setup: fix key-error when changing a new 'section'</title>
<updated>2025-11-06T18:03:46+00:00</updated>
<author>
<name>Johannes Schneider</name>
<email>johannes.schneider@leica-geosystems.com</email>
</author>
<published>2025-11-05T19:06:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=f339e5f07f84862e02d0df74d49705cececb30f0'/>
<id>urn:sha1:f339e5f07f84862e02d0df74d49705cececb30f0</id>
<content type='text'>
Setting a key=value in a new section would raise a key-error when
using in-memory settings, e.g:

./bin/bitbake-setup --setting default top-dir-prefix /tmp/bitbake-setup --setting default top-dir-name gs settings foo bar baz

Loading settings from
    /tmp/bitbake-setup/gs/settings.conf

Traceback (most recent call last):
  File "/tmp/bitbake-setup/bitbake/./bin/bitbake-setup", line 853, in &lt;module&gt;
    main()
  File "/tmp/bitbake-setup/bitbake/./bin/bitbake-setup", line 838, in main
    all_settings = merge_settings(builtin_settings, global_settings, topdir_settings, args.setting)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/tmp/bitbake-setup/bitbake/./bin/bitbake-setup", line 733, in merge_settings
    all_settings[section][setting] = value
    ~~~~~~~~~~~~^^^^^^^^^
KeyError: 'foo'

(Bitbake rev: 78ab0d15dff5ccf64b0bf681185370779e6cabaf)

Signed-off-by: Johannes Schneider &lt;johannes.schneider@leica-geosystems.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: bitbake-setup: rename function 'default_settings_path' to 'topdir_settings_path'</title>
<updated>2025-11-06T18:03:46+00:00</updated>
<author>
<name>Johannes Schneider</name>
<email>johannes.schneider@leica-geosystems.com</email>
</author>
<published>2025-11-05T19:06:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=baee94fa33b8ff41c59845cb2dd2145f18a719ae'/>
<id>urn:sha1:baee94fa33b8ff41c59845cb2dd2145f18a719ae</id>
<content type='text'>
Rename the function to align with the corresponding
'global_settings_path' function, and move it down just above the
later.

This is done to differentiate from the built-in default settings, and
to align with the other places in the code that use 'topdir_settings'
(or 'global_settings')

(Bitbake rev: 3df994f773abbd1d0240e721f5fd29d4b021bfb5)

Signed-off-by: Johannes Schneider &lt;johannes.schneider@leica-geosystems.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: bitbake-setup: rename 'build' -&gt; 'setup'</title>
<updated>2025-11-04T13:16:04+00:00</updated>
<author>
<name>Alexander Kanavin</name>
<email>alex@linutronix.de</email>
</author>
<published>2025-11-04T10:08:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=5d7abe740e26a34216236e0b00f6d2bc001e3156'/>
<id>urn:sha1:5d7abe740e26a34216236e0b00f6d2bc001e3156</id>
<content type='text'>
After a terminology review by Antonin we brainstormed
something less confusing than 'build' and 'build directory'
for the place where bitbake-setup clones layers and
creates a *bitbake* build directory in. People are bound
to get these two confused and mix them up, and 'setup' is
much more distinct and aligns nicely with 'bitbake-setup'.
It's also not claimed by anything else in OE/Yocto.

So before:

top-dir -&gt; build-dir (can be several) -&gt; bitbake build dir, layer dir, config dir

Now:

top-dir -&gt; setup-dir (can be several) -&gt; bitbake build dir, layer dir, config dir

This also updates the respective command line options, I understand it's
a breaking change, but as before the tweaks are simple and we need to get the
terminology right for the users, and now is the time to do it.

(Bitbake rev: eeb81a35bf0304451f7612950d5156ea7ff18bad)

Signed-off-by: Alexander Kanavin &lt;alex@linutronix.de&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: bitbake-setup: correctly define --global argument for settings management</title>
<updated>2025-11-03T17:43:31+00:00</updated>
<author>
<name>Alexander Kanavin</name>
<email>alex@linutronix.de</email>
</author>
<published>2025-10-27T14:16:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=18c39854ef6bc70d2bd456bf4dd778873617e92a'/>
<id>urn:sha1:18c39854ef6bc70d2bd456bf4dd778873617e92a</id>
<content type='text'>
--global was defined twice (for settings command as a whole, and specifically
for set/unset sub-commands), which caused 'settings --global set ...' to
be allowed, and at the same time not have any effect. 'settings set --global'
is the only valid form after this change.

(Bitbake rev: 2f14cf68f6c653b6da90180a99a22c58855b0cef)

Signed-off-by: Alexander Kanavin &lt;alex@linutronix.de&gt;
Tested-by: Antonin Godard &lt;antonin.godard@bootlin.com&gt;
Signed-off-by: Mathieu Dubois-Briand &lt;mathieu.dubois-briand@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: bitbake-setup: commandline: use subsubparser for settings {list,set,unset}</title>
<updated>2025-10-14T10:24:57+00:00</updated>
<author>
<name>Johannes Schneider</name>
<email>johannes.schneider@leica-geosystems.com</email>
</author>
<published>2025-10-12T17:47:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=7320e59aecbaac830d912dd4c0e68b5963c25db4'/>
<id>urn:sha1:7320e59aecbaac830d912dd4c0e68b5963c25db4</id>
<content type='text'>
Previously the sub-command 'settings' would take any number of
arguments and then silently do nothing if the number wasn't three.

The help text was also not clear about this, marking the positionals
separately as optional:

usage: bitbake-setup settings [-h] [--global] [--unset UNSET UNSET] [-l] [section] [key] [value]

The '--unset SECTION SETTING' also did not  integrate too well, as it
had its own positional arguments for section+setting.

For a bit more consistency and a explorable help, a sub-subparser is
added, that provides the commands:
  bitbake-setup settings list
  bitbake-setup settings set foo bar baz
  bitbake-setup settings unset foo bar
with a '--global' that is added from a stand-alone parent parser, so
that it shows up in all sub-command help texts.

The new help text now reads:
usage: bitbake-setup settings [-h] [--global] {list,set,unset} ...

and the respective sub commands:
usage: bitbake-setup settings list [-h] [--global]
usage: bitbake-setup settings set [-h] [--global] &lt;section&gt; &lt;setting&gt; &lt;value&gt;
usage: bitbake-setup settings unset [-h] [--global] &lt;section&gt; &lt;setting&gt;

(Bitbake rev: 8b582ef8dd0cef0192d4c0104bcd9b5d642d132c)

Signed-off-by: Johannes Schneider &lt;johannes.schneider@leica-geosystems.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
