<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/meta/classes-recipe/toolchain-scripts.bbclass, branch master</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=master</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2025-11-07T13:31:53+00:00</updated>
<entry>
<title>The poky repository master branch is no longer being updated.</title>
<updated>2025-11-07T13:31:53+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2025-11-07T13:31:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=8c22ff0d8b70d9b12f0487ef696a7e915b9e3173'/>
<id>urn:sha1:8c22ff0d8b70d9b12f0487ef696a7e915b9e3173</id>
<content type='text'>
You can either:

a) switch to individual clones of bitbake, openembedded-core, meta-yocto and yocto-docs

b) use the new bitbake-setup

You can find information about either approach in our documentation:
https://docs.yoctoproject.org/

Note that "poky" the distro setting is still available in meta-yocto as
before and we continue to use and maintain that.

Long live Poky!

Some further information on the background of this change can be found
in: https://lists.openembedded.org/g/openembedded-architecture/message/2179

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>meta/classes-recipe/toolchain-scripts.bbclass: eliminate bash-ism</title>
<updated>2025-10-09T09:58:07+00:00</updated>
<author>
<name>Alexander Kanavin</name>
<email>alex@linutronix.de</email>
</author>
<published>2025-10-07T18:21:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=9225dc234debc46848e80d697f1d38a0a3c35e7b'/>
<id>urn:sha1:9225dc234debc46848e80d697f1d38a0a3c35e7b</id>
<content type='text'>
Sourcing a script with arguments is a non-standard bash extension
and doesn't work with other shells (e.g. dash, which is used on
Debian and derivatives). This used to work by coincidence when
running against integrated poky repo without having to separately
specify where bitbake is, but no longer does.

Using set is a POSIX standard.

(From OE-Core rev: 933686b7c6307778d171967c49b3a7b6645c31c0)

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>toolchain-scripts.bbclass: fix bitbake-setup compatibility</title>
<updated>2025-10-09T09:58:07+00:00</updated>
<author>
<name>Adrian Freihofer</name>
<email>adrian.freihofer@siemens.com</email>
</author>
<published>2025-10-06T19:10:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=ff0911b191eed695d2214d9892a1bde528b8c9f9'/>
<id>urn:sha1:ff0911b191eed695d2214d9892a1bde528b8c9f9</id>
<content type='text'>
Pass the BITBAKEDIR parameter to oe-init-build-env when called from the
environment-setup script. This fixes compatibility with bitbake-setup,
which places bitbake in a different directory structure than the
standard poky repository layout where bitbake is located alongside
oe-init-build-env.

The issue was discovered when running the oe-selftest test
DevtoolIdeSdkTests.test_devtool_ide_sdk_shared_sysroots, which failed
because the environment-setup script was not able to find bitbake.

File ".../openembedded-core/meta/lib/oeqa/selftest/cases/devtool.py",
  line 2955, in test_devtool_ide_sdk_shared_sysroots
  self.assertExists(cmake_native)
  ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
File ".../openembedded-core/meta/lib/oeqa/selftest/case.py", line 251,
  in assertExists
  raise self.failureException(msg)
AssertionError: 'Error: The bitbake directory (/tmp/devtoolqah9ndff2x/bitbake)
  does not exist!  Please ensure a copy of bitbake exists at this location or
  specify an alternative path on the command line\n
  .../build-st/tmp/sysroots/x86_64/usr/bin/cmake' does not exist

(From OE-Core rev: f31903ca484bad68708ec510e25ea33234f5c0ce)

Signed-off-by: Adrian Freihofer &lt;adrian.freihofer@siemens.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>classes/lib: Switch classextend to use new filter API</title>
<updated>2025-08-12T09:05:11+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2025-06-10T14:53:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=bdb5e99854c76f31d5463f55a657d40098a0743a'/>
<id>urn:sha1:bdb5e99854c76f31d5463f55a657d40098a0743a</id>
<content type='text'>
Currently, class extensions are implmented using shadow variables and
access indirection which is horribly ineffient and ugly.

Switch to using the new bitbake filter API, which allows a translation
of the variable before the expanded value is returned. This allows us
to drop the shadow variable accesses. It also avoids the need to iterate
PACKAGES and make many variable changes since a filter against RDEPENDS
applies to RDEPENDS:${PN} and all of it's other overridden values.

Since data expansion happens at access, it also avoids many of the race
conditions this code has tranditionally been plagued with.

(From OE-Core rev: 24a9858a8927e91d499ee342ed93a0dbb44d83bc)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>toolchain-scripts: Make -mmusl apply only for gcc toolchains</title>
<updated>2025-07-21T22:00:18+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2025-07-18T05:43:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=f5c0e86cc0dd669111a8192cc5dd06c6e9ccd58f'/>
<id>urn:sha1:f5c0e86cc0dd669111a8192cc5dd06c6e9ccd58f</id>
<content type='text'>
This option is not respected by clang

(From OE-Core rev: 82484ccb3eb1a7b5562131881b5ed6545144e5eb)

Signed-off-by: Khem Raj &lt;raj.khem@gmail.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>toolchain-scripts: Export meson settings for SDK builds</title>
<updated>2025-05-12T21:01:55+00:00</updated>
<author>
<name>Tom Hochstein</name>
<email>tom.hochstein@oss.nxp.com</email>
</author>
<published>2025-05-10T08:43:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=12bcad4ea5a9d413a08375cc14c56d3158466d0c'/>
<id>urn:sha1:12bcad4ea5a9d413a08375cc14c56d3158466d0c</id>
<content type='text'>
Create a new set of exports for the Meson `host_machine` cross settings.
This allows the target cross file to be created correctly from
meson.cross.template and aligns with meson.bbclass.

Note, one might think that HOST_OS and HOST_ARCH would be appropriate as
inputs here, aligning nicely with the Meson naming. That turns out to be
incorrect since the script is generated in a native/nativesdk build with
HOST_OS and HOST_ARCH set for the "build machine", not the "host
machine", using the Meson terminology. See
https://mesonbuild.com/Cross-compilation.html.

Fixes: [YOCTO #15485]
(From OE-Core rev: 9e742a0a9078f4a19a5edbfa51f22f7b71992188)

(From OE-Core rev: f2f898e36feb3bd489edda451e71b11bf69940b9)

Signed-off-by: Tom Hochstein &lt;tom.hochstein@oss.nxp.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>toolchain-scripts: Add Meson settings for Yocto build SDK</title>
<updated>2025-05-12T21:01:55+00:00</updated>
<author>
<name>Tom Hochstein</name>
<email>tom.hochstein@oss.nxp.com</email>
</author>
<published>2025-05-10T08:43:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=4f8de83f4ffa5a9d20dc80073d6d774f8dce10db'/>
<id>urn:sha1:4f8de83f4ffa5a9d20dc80073d6d774f8dce10db</id>
<content type='text'>
The Meson settings for the standalone SDK also need to be available for
the Yocto build SDK, a.k.a. meta-ide-support.

(From OE-Core rev: 6287114bf10718fe49f7c1ed211f3d99f0933bc4)

(From OE-Core rev: d69d049e9a7114323a1e1b8da4999e9e3f08ad03)

Signed-off-by: Tom Hochstein &lt;tom.hochstein@oss.nxp.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>siteconfig: Drop siteconfig class/code/support</title>
<updated>2024-05-31T15:58:36+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2024-05-30T16:15:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=6b9eb4e9f04387b68e1b55e06b0d91edfa572abb'/>
<id>urn:sha1:6b9eb4e9f04387b68e1b55e06b0d91edfa572abb</id>
<content type='text'>
The siteconfig code was only used for 5 cache values. The complexity added to sstate
to support this code was considerable and the runtime much more significant than
any benefit the cache files would have added. Drop the support for this which
was only used minimally for ncurses and zlib.

(From OE-Core rev: f3766dc038f7ba9780ddaf5eb8d27385ea31d7d0)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>toolchain-scripts: export the target endianism and word size</title>
<updated>2024-05-22T09:21:26+00:00</updated>
<author>
<name>Ross Burton</name>
<email>ross.burton@arm.com</email>
</author>
<published>2024-05-20T10:18:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=e1fa32477dcbdb317f858de2265be10c42ba91a4'/>
<id>urn:sha1:e1fa32477dcbdb317f858de2265be10c42ba91a4</id>
<content type='text'>
Some build systems (notably, Meson) like to be told when cross-compiling
what the target endian and word size is.  We don't have these exported
via the variables, so add them using siteinfo as a source of data.

(From OE-Core rev: c2fee816cae6dbedcb40f15be4a1b9ee91757a64)

Signed-off-by: Ross Burton &lt;ross.burton@arm.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>toolchain-scripts: Handle spaces within user $PATH</title>
<updated>2023-03-11T00:08:41+00:00</updated>
<author>
<name>Kenfe-Mickael Laventure</name>
<email>mickael.laventure@gmail.com</email>
</author>
<published>2023-03-09T19:49:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=aa484fd4159ba1620d84164ed2092edb7c5075ca'/>
<id>urn:sha1:aa484fd4159ba1620d84164ed2092edb7c5075ca</id>
<content type='text'>
The environment-setup script generated by the recipe was not quoting the
user existing PATH when updating it causing the export command to fail.

Add necessary double quotes around $PATH.

(From OE-Core rev: 42177ff2d45ee70ad00917bb6fbabca49dae4f59)

Signed-off-by: Kenfe-Mickael Laventure &lt;mickael.laventure@gmail.com&gt;
Signed-off-by: Alexandre Belloni &lt;alexandre.belloni@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
