summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
Diffstat (limited to 'documentation')
-rw-r--r--documentation/dev-manual/start.rst4
-rw-r--r--documentation/dev-manual/vulnerabilities.rst2
-rw-r--r--documentation/migration-guides/migration-5.3.rst47
-rw-r--r--documentation/migration-guides/release-5.2.rst2
-rw-r--r--documentation/migration-guides/release-notes-5.2.4.rst320
-rw-r--r--documentation/migration-guides/release-notes-5.3.rst336
-rw-r--r--documentation/overview-manual/yp-intro.rst11
-rw-r--r--documentation/ref-manual/classes.rst191
-rw-r--r--documentation/ref-manual/features.rst8
-rw-r--r--documentation/ref-manual/qa-checks.rst11
-rw-r--r--documentation/ref-manual/variables.rst152
-rw-r--r--documentation/test-manual/reproducible-builds.rst2
-rw-r--r--documentation/test-manual/test-process.rst2
13 files changed, 1016 insertions, 72 deletions
diff --git a/documentation/dev-manual/start.rst b/documentation/dev-manual/start.rst
index 77ba16e2f5..2a1be7260e 100644
--- a/documentation/dev-manual/start.rst
+++ b/documentation/dev-manual/start.rst
@@ -653,8 +653,8 @@ described in the ":ref:`dev-manual/start:accessing source archives`" section.
653#. *Get to the Downloads Area:* Select the "RELEASES" item from the 653#. *Get to the Downloads Area:* Select the "RELEASES" item from the
654 pull-down "DEVELOPMENT" tab menu near the top of the page. 654 pull-down "DEVELOPMENT" tab menu near the top of the page.
655 655
656#. *Select a Yocto Project Release:* On the top of the "RELEASE" page currently 656#. *Select a Yocto Project Release:* On the top of the "RELEASES" page, currently
657 supported releases are displayed, further down past supported Yocto Project 657 supported releases are displayed; further down, past supported Yocto Project
658 releases are visible. The "Download" links in the rows of the table there 658 releases are visible. The "Download" links in the rows of the table there
659 will lead to the download tarballs for the release. 659 will lead to the download tarballs for the release.
660 660
diff --git a/documentation/dev-manual/vulnerabilities.rst b/documentation/dev-manual/vulnerabilities.rst
index 6cc7f04944..3a83a40f31 100644
--- a/documentation/dev-manual/vulnerabilities.rst
+++ b/documentation/dev-manual/vulnerabilities.rst
@@ -12,7 +12,7 @@ known security vulnerabilities, as tracked by the public
12database. 12database.
13 13
14The Yocto Project maintains a `list of known vulnerabilities 14The Yocto Project maintains a `list of known vulnerabilities
15<https://autobuilder.yocto.io/pub/non-release/patchmetrics/>`__ 15<https://valkyrie.yocto.io/pub/non-release/patchmetrics/>`__
16for packages in Poky and OE-Core, tracking the evolution of the number of 16for packages in Poky and OE-Core, tracking the evolution of the number of
17unpatched CVEs and the status of patches. Such information is available for 17unpatched CVEs and the status of patches. Such information is available for
18the current development version and for each supported release. 18the current development version and for each supported release.
diff --git a/documentation/migration-guides/migration-5.3.rst b/documentation/migration-guides/migration-5.3.rst
index 985712cb22..e59bc8c638 100644
--- a/documentation/migration-guides/migration-5.3.rst
+++ b/documentation/migration-guides/migration-5.3.rst
@@ -134,10 +134,20 @@ To set back the "mac" policy in systemd (version 257.8 at the time of writing
134this note), you should set the ``NamePolicy`` and ``AlternativeNamesPolicy`` as 134this note), you should set the ``NamePolicy`` and ``AlternativeNamesPolicy`` as
135detailed in :manpage:`systemd.link(5)`. 135detailed in :manpage:`systemd.link(5)`.
136 136
137Removal of unlicensed Linux kernel firmware
138~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
139
140By default, the ``linux-firmware`` recipe now excludes firmware that do not
141provide any license information. The recipe holds an internal list of firmware
142to exclude via a variable named ``REMOVE_UNLICENSED``, this variable may be
143overridden if unlicensed firmware is needed. See :oe_git:`the recipe
144</openembedded-core/tree/meta/recipes-kernel/linux-firmware>` for a complete
145overview of the removed firmware.
146
137Supported kernel versions 147Supported kernel versions
138~~~~~~~~~~~~~~~~~~~~~~~~~ 148~~~~~~~~~~~~~~~~~~~~~~~~~
139 149
140The :term:`OLDEST_KERNEL` setting is XXX in this release, meaning that 150The :term:`OLDEST_KERNEL` setting is 5.15 in this release, meaning that
141out the box, older kernels are not supported. See :ref:`4.3 migration notes 151out the box, older kernels are not supported. See :ref:`4.3 migration notes
142<migration-4.3-supported-kernel-versions>` for details. 152<migration-4.3-supported-kernel-versions>` for details.
143 153
@@ -147,7 +157,9 @@ Supported distributions
147Compared to the previous releases, running BitBake is supported on new 157Compared to the previous releases, running BitBake is supported on new
148GNU/Linux distributions: 158GNU/Linux distributions:
149 159
150- XXX 160- Debian 13 (Trixie)
161- Fedora 42
162- Ubuntu 25.04
151 163
152On the other hand, some earlier distributions are no longer supported: 164On the other hand, some earlier distributions are no longer supported:
153 165
@@ -174,6 +186,10 @@ The following variables have been removed:
174 :term:`BitBake` invocation and replace it with information about what was 186 :term:`BitBake` invocation and replace it with information about what was
175 built during the build. This was partly broken and hard to maintain. 187 built during the build. This was partly broken and hard to maintain.
176 188
189- ``GPE_MIRROR``: this variable used to contain the
190 "http://gpe.linuxtogo.org/download/source" URL, but was not used by any
191 recipe in OE-Core.
192
177Removed recipes 193Removed recipes
178~~~~~~~~~~~~~~~ 194~~~~~~~~~~~~~~~
179 195
@@ -195,6 +211,11 @@ The following recipes have been removed in this release:
195- ``xf86-input-vmmouse``: It has a runtime dependency on ``xf86-input-mouse``, 211- ``xf86-input-vmmouse``: It has a runtime dependency on ``xf86-input-mouse``,
196 which stopped supporting Linux. 212 which stopped supporting Linux.
197 213
214- ``babeltrace``: Removed in favour of ``babeltrace2``.
215
216- ``cwautomacros``: A long-obsolete set of custom :ref:`ref-classes-autotools`
217 macros, not used by any other recipe.
218
198Removed :term:`PACKAGECONFIG` entries 219Removed :term:`PACKAGECONFIG` entries
199~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 220~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
200 221
@@ -206,6 +227,8 @@ Removed :term:`PACKAGECONFIG` entries
206 227
207- ``mesa``: ``kmsro``, ``osmesa``, ``xa`` 228- ``mesa``: ``kmsro``, ``osmesa``, ``xa``
208 229
230- ``systemd``: ``dbus``
231
209Removed classes 232Removed classes
210~~~~~~~~~~~~~~~ 233~~~~~~~~~~~~~~~
211 234
@@ -269,4 +292,22 @@ Miscellaneous changes
269- ``xserver-xorg``: remove sub-package ``${PN}-xwayland``, as ``xwayland`` is 292- ``xserver-xorg``: remove sub-package ``${PN}-xwayland``, as ``xwayland`` is
270 now its own recipe. 293 now its own recipe.
271 294
272- The Wic-specific option ``--extra-space`` has been renamed to ``--extra-filesystem-space``. \ No newline at end of file 295- ``gdk-pixbuf``: drop the ``GDK_PIXBUF_LOADERS`` variable, which was part of
296 the recipe's :term:`PACKAGECONFIG`. Instead the :term:`PACKAGECONFIG` can be
297 modified directly to achieve the same result.
298
299- Remove the ``meta/conf/distro/include/distro_alias.inc`` include file,
300 which associated a recipe name to one or more Distribution package name.
301 This file is not used and maintained anymore.
302
303- Remove the ``nghttp2-proxy`` package from the ``nghttp2`` recipe as the
304 ``nghttp2-proxy`` package became empty after an upgrade that makes it a
305 library recipe only (due to
306 :term:`EXTRA_OEMAKE` containing ``-DENABLE_APP=OFF`` by default in the
307 recipe).
308
309- Remove the ``util-linux-fcntl-lock`` package (in the ``util-linux`` recipe) as
310 ``util-linux`` now supports the ``--fcntl`` flag for the ``flock`` command.
311
312 Recipes currently using the ``fcntl-lock`` command should replace these by
313 ``flock --fcntl``.
diff --git a/documentation/migration-guides/release-5.2.rst b/documentation/migration-guides/release-5.2.rst
index 745251ed76..2c2729fbd9 100644
--- a/documentation/migration-guides/release-5.2.rst
+++ b/documentation/migration-guides/release-5.2.rst
@@ -10,4 +10,4 @@ Release 5.2 (walnascar)
10 release-notes-5.2.1 10 release-notes-5.2.1
11 release-notes-5.2.2 11 release-notes-5.2.2
12 release-notes-5.2.3 12 release-notes-5.2.3
13 13 release-notes-5.2.4
diff --git a/documentation/migration-guides/release-notes-5.2.4.rst b/documentation/migration-guides/release-notes-5.2.4.rst
new file mode 100644
index 0000000000..eaaae6a819
--- /dev/null
+++ b/documentation/migration-guides/release-notes-5.2.4.rst
@@ -0,0 +1,320 @@
1Release notes for Yocto-5.2.4 (Walnascar)
2-----------------------------------------
3
4Security Fixes in Yocto-5.2.4
5~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
6
7- binutils: Fix :cve_nist:`2025-8225`
8- binutils: Ignore :cve_nist:`2025-8224`
9- cups: Fix :cve_nist:`2025-58060` and :cve_nist:`2025-58364`
10- curl: Fix :cve_nist:`2025-9086` and :cve_nist:`2025-10148`
11- elfutils: Fix :cve_nist:`2025-1352`, :cve_nist:`2025-1365`, :cve_nist:`2025-1371`,
12 :cve_nist:`2025-1372`, :cve_nist:`2025-1376` and :cve_nist:`2025-1377`
13- expat: Fix :cve_nist:`2025-59375`
14- ffmpeg: Fix CVE-2025-7700
15- glib-2.0: Fix :cve_nist:`2025-4056`, :cve_nist:`2025-6052` and :cve_nist:`2025-7039`
16- gnutls: Ignore :cve_nist:`2025-32989` and :cve_nist:`2025-32990`
17- grub2: Fix :cve_nist:`2024-56738`
18- grub2: Ignore :cve_nist:`2024-2312`
19- gstreamer1.0: Ignore :cve_nist:`2025-2759`, :cve_nist:`2025-3887`, :cve_nist:`2025-47183`,
20 :cve_nist:`2025-47219`, :cve_nist:`2025-47806`, :cve_nist:`2025-47807` and :cve_nist:`2025-47808`
21- libarchive: Fix :cve_nist:`2025-5916`, :cve_nist:`2025-5917` and :cve_nist:`2025-5918`
22- libpre2: Fix :cve_nist:`2025-58050`
23- linux-yocto/6.12: Ignore :cve_nist:`2022-50233`, :cve_nist:`2023-3865`, :cve_nist:`2023-3866`,
24 :cve_nist:`2023-3867`, :cve_nist:`2023-4130`, :cve_nist:`2023-4515`, :cve_nist:`2023-32246`,
25 :cve_nist:`2023-32249`, :cve_nist:`2024-58238`, :cve_nist:`2024-58239`, :cve_nist:`2024-58240`,
26 :cve_nist:`2025-21884`, :cve_nist:`2025-22103`, :cve_nist:`2025-22113`, :cve_nist:`2025-22115`,
27 :cve_nist:`2025-22124`, :cve_nist:`2025-22125`, :cve_nist:`2025-23133`, :cve_nist:`2025-37925`,
28 :cve_nist:`2025-37984`, :cve_nist:`2025-38067`, :cve_nist:`2025-38104`, :cve_nist:`2025-38272`,
29 :cve_nist:`2025-38306`, :cve_nist:`2025-38335`, :cve_nist:`2025-38349`, :cve_nist:`2025-38350`,
30 :cve_nist:`2025-38351`, :cve_nist:`2025-38352`, :cve_nist:`2025-38353`, :cve_nist:`2025-38354`,
31 :cve_nist:`2025-38355`, :cve_nist:`2025-38356`, :cve_nist:`2025-38357`, :cve_nist:`2025-38358`,
32 :cve_nist:`2025-38360`, :cve_nist:`2025-38361`, :cve_nist:`2025-38362`, :cve_nist:`2025-38363`,
33 :cve_nist:`2025-38364`, :cve_nist:`2025-38365`, :cve_nist:`2025-38366`, :cve_nist:`2025-38367`,
34 :cve_nist:`2025-38368`, :cve_nist:`2025-38369`, :cve_nist:`2025-38370`, :cve_nist:`2025-38371`,
35 :cve_nist:`2025-38372`, :cve_nist:`2025-38373`, :cve_nist:`2025-38374`, :cve_nist:`2025-38375`,
36 :cve_nist:`2025-38376`, :cve_nist:`2025-38377`, :cve_nist:`2025-38378`, :cve_nist:`2025-38379`,
37 :cve_nist:`2025-38380`, :cve_nist:`2025-38381`, :cve_nist:`2025-38382`, :cve_nist:`2025-38383`,
38 :cve_nist:`2025-38384`, :cve_nist:`2025-38385`, :cve_nist:`2025-38386`, :cve_nist:`2025-38387`,
39 :cve_nist:`2025-38388`, :cve_nist:`2025-38389`, :cve_nist:`2025-38390`, :cve_nist:`2025-38391`,
40 :cve_nist:`2025-38392`, :cve_nist:`2025-38393`, :cve_nist:`2025-38394`, :cve_nist:`2025-38395`,
41 :cve_nist:`2025-38396`, :cve_nist:`2025-38397`, :cve_nist:`2025-38398`, :cve_nist:`2025-38399`,
42 :cve_nist:`2025-38400`, :cve_nist:`2025-38401`, :cve_nist:`2025-38402`, :cve_nist:`2025-38403`,
43 :cve_nist:`2025-38404`, :cve_nist:`2025-38405`, :cve_nist:`2025-38406`, :cve_nist:`2025-38407`,
44 :cve_nist:`2025-38408`, :cve_nist:`2025-38409`, :cve_nist:`2025-38410`, :cve_nist:`2025-38411`,
45 :cve_nist:`2025-38412`, :cve_nist:`2025-38413`, :cve_nist:`2025-38414`, :cve_nist:`2025-38415`,
46 :cve_nist:`2025-38416`, :cve_nist:`2025-38417`, :cve_nist:`2025-38418`, :cve_nist:`2025-38419`,
47 :cve_nist:`2025-38420`, :cve_nist:`2025-38421`, :cve_nist:`2025-38422`, :cve_nist:`2025-38423`,
48 :cve_nist:`2025-38424`, :cve_nist:`2025-38425`, :cve_nist:`2025-38427`, :cve_nist:`2025-38428`,
49 :cve_nist:`2025-38429`, :cve_nist:`2025-38430`, :cve_nist:`2025-38431`, :cve_nist:`2025-38432`,
50 :cve_nist:`2025-38433`, :cve_nist:`2025-38434`, :cve_nist:`2025-38435`, :cve_nist:`2025-38436`,
51 :cve_nist:`2025-38437`, :cve_nist:`2025-38438`, :cve_nist:`2025-38439`, :cve_nist:`2025-38440`,
52 :cve_nist:`2025-38441`, :cve_nist:`2025-38442`, :cve_nist:`2025-38443`, :cve_nist:`2025-38444`,
53 :cve_nist:`2025-38445`, :cve_nist:`2025-38446`, :cve_nist:`2025-38447`, :cve_nist:`2025-38448`,
54 :cve_nist:`2025-38449`, :cve_nist:`2025-38450`, :cve_nist:`2025-38451`, :cve_nist:`2025-38452`,
55 :cve_nist:`2025-38453`, :cve_nist:`2025-38454`, :cve_nist:`2025-38455`, :cve_nist:`2025-38456`,
56 :cve_nist:`2025-38457`, :cve_nist:`2025-38458`, :cve_nist:`2025-38459`, :cve_nist:`2025-38460`,
57 :cve_nist:`2025-38461`, :cve_nist:`2025-38462`, :cve_nist:`2025-38463`, :cve_nist:`2025-38464`,
58 :cve_nist:`2025-38465`, :cve_nist:`2025-38466`, :cve_nist:`2025-38467`, :cve_nist:`2025-38468`,
59 :cve_nist:`2025-38469`, :cve_nist:`2025-38470`, :cve_nist:`2025-38471`, :cve_nist:`2025-38472`,
60 :cve_nist:`2025-38473`, :cve_nist:`2025-38474`, :cve_nist:`2025-38475`, :cve_nist:`2025-38476`,
61 :cve_nist:`2025-38477`, :cve_nist:`2025-38478`, :cve_nist:`2025-38480`, :cve_nist:`2025-38481`,
62 :cve_nist:`2025-38482`, :cve_nist:`2025-38483`, :cve_nist:`2025-38484`, :cve_nist:`2025-38485`,
63 :cve_nist:`2025-38486`, :cve_nist:`2025-38487`, :cve_nist:`2025-38488`, :cve_nist:`2025-38489`,
64 :cve_nist:`2025-38490`, :cve_nist:`2025-38491`, :cve_nist:`2025-38492`, :cve_nist:`2025-38493`,
65 :cve_nist:`2025-38494`, :cve_nist:`2025-38495`, :cve_nist:`2025-38496`, :cve_nist:`2025-38497`,
66 :cve_nist:`2025-38498`, :cve_nist:`2025-38499`, :cve_nist:`2025-38500`, :cve_nist:`2025-38501`,
67 :cve_nist:`2025-38502`, :cve_nist:`2025-38503`, :cve_nist:`2025-38504`, :cve_nist:`2025-38505`,
68 :cve_nist:`2025-38506`, :cve_nist:`2025-38507`, :cve_nist:`2025-38508`, :cve_nist:`2025-38509`,
69 :cve_nist:`2025-38510`, :cve_nist:`2025-38511`, :cve_nist:`2025-38512`, :cve_nist:`2025-38513`,
70 :cve_nist:`2025-38514`, :cve_nist:`2025-38515`, :cve_nist:`2025-38516`, :cve_nist:`2025-38517`,
71 :cve_nist:`2025-38518`, :cve_nist:`2025-38519`, :cve_nist:`2025-38520`, :cve_nist:`2025-38521`,
72 :cve_nist:`2025-38522`, :cve_nist:`2025-38523`, :cve_nist:`2025-38524`, :cve_nist:`2025-38525`,
73 :cve_nist:`2025-38526`, :cve_nist:`2025-38527`, :cve_nist:`2025-38528`, :cve_nist:`2025-38529`,
74 :cve_nist:`2025-38530`, :cve_nist:`2025-38531`, :cve_nist:`2025-38532`, :cve_nist:`2025-38533`,
75 :cve_nist:`2025-38534`, :cve_nist:`2025-38535`, :cve_nist:`2025-38536`, :cve_nist:`2025-38537`,
76 :cve_nist:`2025-38538`, :cve_nist:`2025-38539`, :cve_nist:`2025-38540`, :cve_nist:`2025-38541`,
77 :cve_nist:`2025-38542`, :cve_nist:`2025-38543`, :cve_nist:`2025-38544`, :cve_nist:`2025-38545`,
78 :cve_nist:`2025-38546`, :cve_nist:`2025-38547`, :cve_nist:`2025-38548`, :cve_nist:`2025-38549`,
79 :cve_nist:`2025-38550`, :cve_nist:`2025-38551`, :cve_nist:`2025-38552`, :cve_nist:`2025-38553`,
80 :cve_nist:`2025-38554`, :cve_nist:`2025-38555`, :cve_nist:`2025-38556`, :cve_nist:`2025-38557`,
81 :cve_nist:`2025-38558`, :cve_nist:`2025-38559`, :cve_nist:`2025-38560`, :cve_nist:`2025-38561`,
82 :cve_nist:`2025-38562`, :cve_nist:`2025-38563`, :cve_nist:`2025-38564`, :cve_nist:`2025-38565`,
83 :cve_nist:`2025-38566`, :cve_nist:`2025-38567`, :cve_nist:`2025-38568`, :cve_nist:`2025-38569`,
84 :cve_nist:`2025-38570`, :cve_nist:`2025-38571`, :cve_nist:`2025-38572`, :cve_nist:`2025-38573`,
85 :cve_nist:`2025-38574`, :cve_nist:`2025-38576`, :cve_nist:`2025-38577`, :cve_nist:`2025-38578`,
86 :cve_nist:`2025-38579`, :cve_nist:`2025-38580`, :cve_nist:`2025-38581`, :cve_nist:`2025-38582`,
87 :cve_nist:`2025-38583`, :cve_nist:`2025-38585`, :cve_nist:`2025-38586`, :cve_nist:`2025-38587`,
88 :cve_nist:`2025-38588`, :cve_nist:`2025-38589`, :cve_nist:`2025-38590`, :cve_nist:`2025-38592`,
89 :cve_nist:`2025-38593`, :cve_nist:`2025-38594`, :cve_nist:`2025-38595`, :cve_nist:`2025-38596`,
90 :cve_nist:`2025-38598` and :cve_nist:`2025-38599`
91- linux-yocto/6.12: Ignore :cve_nist:`2025-38600`, :cve_nist:`2025-38601`, :cve_nist:`2025-38602`,
92 :cve_nist:`2025-38603`, :cve_nist:`2025-38604`, :cve_nist:`2025-38606`, :cve_nist:`2025-38607`,
93 :cve_nist:`2025-38608`, :cve_nist:`2025-38609`, :cve_nist:`2025-38610`, :cve_nist:`2025-38611`,
94 :cve_nist:`2025-38612`, :cve_nist:`2025-38613`, :cve_nist:`2025-38614`, :cve_nist:`2025-38615`,
95 :cve_nist:`2025-38616`, :cve_nist:`2025-38617`, :cve_nist:`2025-38618`, :cve_nist:`2025-38619`,
96 :cve_nist:`2025-38620`, :cve_nist:`2025-38622`, :cve_nist:`2025-38623`, :cve_nist:`2025-38624`,
97 :cve_nist:`2025-38625`, :cve_nist:`2025-38626`, :cve_nist:`2025-38628`, :cve_nist:`2025-38629`,
98 :cve_nist:`2025-38630`, :cve_nist:`2025-38631`, :cve_nist:`2025-38632`, :cve_nist:`2025-38633`,
99 :cve_nist:`2025-38634`, :cve_nist:`2025-38635`, :cve_nist:`2025-38638`, :cve_nist:`2025-38639`,
100 :cve_nist:`2025-38640`, :cve_nist:`2025-38641`, :cve_nist:`2025-38642`, :cve_nist:`2025-38644`,
101 :cve_nist:`2025-38645`, :cve_nist:`2025-38646`, :cve_nist:`2025-38647`, :cve_nist:`2025-38648`,
102 :cve_nist:`2025-38649`, :cve_nist:`2025-38650`, :cve_nist:`2025-38651`, :cve_nist:`2025-38652`,
103 :cve_nist:`2025-38653`, :cve_nist:`2025-38654`, :cve_nist:`2025-38655`, :cve_nist:`2025-38657`,
104 :cve_nist:`2025-38658`, :cve_nist:`2025-38659`, :cve_nist:`2025-38660`, :cve_nist:`2025-38661`,
105 :cve_nist:`2025-38662`, :cve_nist:`2025-38663`, :cve_nist:`2025-38664`, :cve_nist:`2025-38665`,
106 :cve_nist:`2025-38666`, :cve_nist:`2025-38667`, :cve_nist:`2025-38668`, :cve_nist:`2025-38669`,
107 :cve_nist:`2025-38670`, :cve_nist:`2025-38671`, :cve_nist:`2025-38672`, :cve_nist:`2025-38673`,
108 :cve_nist:`2025-38674`, :cve_nist:`2025-38675`, :cve_nist:`2025-38676`, :cve_nist:`2025-38677`,
109 :cve_nist:`2025-38679`, :cve_nist:`2025-38680`, :cve_nist:`2025-38681`, :cve_nist:`2025-38682`,
110 :cve_nist:`2025-38683`, :cve_nist:`2025-38684`, :cve_nist:`2025-38685`, :cve_nist:`2025-38686`,
111 :cve_nist:`2025-38687`, :cve_nist:`2025-38688`, :cve_nist:`2025-38689`, :cve_nist:`2025-38690`,
112 :cve_nist:`2025-38691`, :cve_nist:`2025-38692`, :cve_nist:`2025-38693`, :cve_nist:`2025-38694`,
113 :cve_nist:`2025-38695`, :cve_nist:`2025-38696`, :cve_nist:`2025-38697`, :cve_nist:`2025-38698`,
114 :cve_nist:`2025-38699`, :cve_nist:`2025-38700`, :cve_nist:`2025-38701`, :cve_nist:`2025-38702`,
115 :cve_nist:`2025-38703`, :cve_nist:`2025-38704`, :cve_nist:`2025-38705`, :cve_nist:`2025-38706`,
116 :cve_nist:`2025-38707`, :cve_nist:`2025-38708`, :cve_nist:`2025-38709`, :cve_nist:`2025-38710`,
117 :cve_nist:`2025-38711`, :cve_nist:`2025-38712`, :cve_nist:`2025-38713`, :cve_nist:`2025-38714`,
118 :cve_nist:`2025-38715`, :cve_nist:`2025-38716`, :cve_nist:`2025-38717`, :cve_nist:`2025-38718`,
119 :cve_nist:`2025-38719`, :cve_nist:`2025-38720`, :cve_nist:`2025-38721`, :cve_nist:`2025-38722`,
120 :cve_nist:`2025-38723`, :cve_nist:`2025-38724`, :cve_nist:`2025-38725`, :cve_nist:`2025-38726`,
121 :cve_nist:`2025-38727`, :cve_nist:`2025-38728`, :cve_nist:`2025-38729`, :cve_nist:`2025-38730`,
122 :cve_nist:`2025-38731`, :cve_nist:`2025-38732`, :cve_nist:`2025-38733`, :cve_nist:`2025-38734`,
123 :cve_nist:`2025-38735`, :cve_nist:`2025-38736`, :cve_nist:`2025-38737`, :cve_nist:`2025-39673`,
124 :cve_nist:`2025-39674`, :cve_nist:`2025-39675`, :cve_nist:`2025-39676`, :cve_nist:`2025-39679`,
125 :cve_nist:`2025-39680`, :cve_nist:`2025-39681`, :cve_nist:`2025-39682`, :cve_nist:`2025-39683`,
126 :cve_nist:`2025-39684`, :cve_nist:`2025-39685`, :cve_nist:`2025-39686`, :cve_nist:`2025-39687`,
127 :cve_nist:`2025-39689`, :cve_nist:`2025-39690`, :cve_nist:`2025-39691`, :cve_nist:`2025-39692`,
128 :cve_nist:`2025-39693`, :cve_nist:`2025-39694`, :cve_nist:`2025-39695`, :cve_nist:`2025-39696`,
129 :cve_nist:`2025-39697`, :cve_nist:`2025-39698`, :cve_nist:`2025-39699`, :cve_nist:`2025-39700`,
130 :cve_nist:`2025-39701`, :cve_nist:`2025-39702`, :cve_nist:`2025-39703`, :cve_nist:`2025-39704`,
131 :cve_nist:`2025-39705`, :cve_nist:`2025-39706`, :cve_nist:`2025-39707`, :cve_nist:`2025-39708`,
132 :cve_nist:`2025-39709`, :cve_nist:`2025-39710`, :cve_nist:`2025-39711`, :cve_nist:`2025-39712`,
133 :cve_nist:`2025-39713`, :cve_nist:`2025-39714`, :cve_nist:`2025-39715`, :cve_nist:`2025-39716`,
134 :cve_nist:`2025-39717`, :cve_nist:`2025-39718`, :cve_nist:`2025-39719`, :cve_nist:`2025-39720`,
135 :cve_nist:`2025-39721`, :cve_nist:`2025-39722`, :cve_nist:`2025-39723`, :cve_nist:`2025-39724`,
136 :cve_nist:`2025-39725`, :cve_nist:`2025-39726`, :cve_nist:`2025-39727`, :cve_nist:`2025-39729`,
137 :cve_nist:`2025-39730`, :cve_nist:`2025-39731`, :cve_nist:`2025-39732`, :cve_nist:`2025-39733`,
138 :cve_nist:`2025-39734`, :cve_nist:`2025-39736`, :cve_nist:`2025-39737`, :cve_nist:`2025-39738`,
139 :cve_nist:`2025-39739`, :cve_nist:`2025-39740`, :cve_nist:`2025-39741`, :cve_nist:`2025-39742`,
140 :cve_nist:`2025-39743`, :cve_nist:`2025-39744`, :cve_nist:`2025-39746`, :cve_nist:`2025-39747`,
141 :cve_nist:`2025-39748`, :cve_nist:`2025-39749`, :cve_nist:`2025-39750`, :cve_nist:`2025-39751`,
142 :cve_nist:`2025-39752`, :cve_nist:`2025-39753`, :cve_nist:`2025-39754`, :cve_nist:`2025-39756`,
143 :cve_nist:`2025-39757`, :cve_nist:`2025-39758`, :cve_nist:`2025-39759`, :cve_nist:`2025-39760`,
144 :cve_nist:`2025-39761`, :cve_nist:`2025-39763`, :cve_nist:`2025-39765`, :cve_nist:`2025-39766`,
145 :cve_nist:`2025-39767`, :cve_nist:`2025-39768`, :cve_nist:`2025-39769`, :cve_nist:`2025-39770`,
146 :cve_nist:`2025-39771`, :cve_nist:`2025-39772`, :cve_nist:`2025-39773`, :cve_nist:`2025-39774`,
147 :cve_nist:`2025-39775`, :cve_nist:`2025-39776`, :cve_nist:`2025-39777`, :cve_nist:`2025-39779`,
148 :cve_nist:`2025-39780`, :cve_nist:`2025-39781`, :cve_nist:`2025-39782`, :cve_nist:`2025-39783`,
149 :cve_nist:`2025-39784`, :cve_nist:`2025-39785`, :cve_nist:`2025-39786`, :cve_nist:`2025-39787`,
150 :cve_nist:`2025-39788`, :cve_nist:`2025-39790`, :cve_nist:`2025-39791`, :cve_nist:`2025-39792`,
151 :cve_nist:`2025-39793`, :cve_nist:`2025-39794`, :cve_nist:`2025-39795`, :cve_nist:`2025-39796`,
152 :cve_nist:`2025-39797`, :cve_nist:`2025-39798` and :cve_nist:`2025-39799`
153- libxslt: Fix :cve_nist:`2025-7424`
154- pulseaudio: Ignore :cve_nist:`2024-11586`
155- tiff: Fix :cve_nist:`2024-13978`, :cve_nist:`2025-8176`, :cve_nist:`2025-8177`,
156 :cve_nist:`2025-8534`, :cve_nist:`2025-8961` and :cve_nist:`2025-9165`
157- tiff: Ignore :cve_nist:`2025-8851`
158- vim: Fix :cve_nist:`2025-53905`, :cve_nist:`2025-53906`, :cve_nist:`2025-55157` and
159 :cve_nist:`2025-55158`
160
161
162Fixes in Yocto-5.2.4
163~~~~~~~~~~~~~~~~~~~~
164
165- bash: use -std=gnu17 also for native :term:`CFLAGS`
166- binutils: Fix gprofng broken symbolic link with gp-*
167- bitbake: Use a "fork" multiprocessing context
168- bitbake: bitbake: Bump version to 2.12.1
169- bitbake: tests/fetch: Update tests after bitbake tag removal
170- build-appliance-image: Update to walnascar head revision
171- buildtools-tarball: fix unbound variable issues under 'set -u'
172- cve-update-db-native: Fix fetcher for CVEs missing nodes
173- default-distrovars.inc: Fix CONNECTIVITY_CHECK_URIS redirect issue
174- dev-manual/security-subjects.rst: update mailing lists
175- expat: upgrade to 2.7.2
176- ffmpeg: upgrade to 7.1.2
177- glib-2.0: update to 2.84.4
178- go: upgrade 1.24.6
179- gst-devtools: upgrade 1.24.13
180- gstreamer1.0-libav: upgrade 1.24.13
181- gstreamer1.0-plugins-bad: upgrade 1.24.13
182- gstreamer1.0-plugins-base: upgrade 1.24.13
183- gstreamer1.0-plugins-good: upgrade 1.24.13
184- gstreamer1.0-plugins-ugly: upgrade 1.24.13
185- gstreamer1.0-python: upgrade 1.24.13
186- gstreamer1.0-rtsp-server: upgrade 1.24.13
187- gstreamer1.0-vaapi: upgrade 1.24.13
188- gstreamer1.0: upgrade 1.24.13
189- lib/oe/utils: use multiprocessing from bb
190- libpcre2: upgrade 10.46
191- license.py: avoid deprecated ast.Str
192- linux-firmware: fix :term:`FILES` to drop :term:`RDEPENDS` on full package
193- linux-yocto/6.12: Revert "linux-yocto/6.12: riscv: Enable :term:`TUNE_FEATURES` based
194 KERNEL_FEATURES"
195- linux-yocto/6.12: update to 6.12.47
196- migration-guides: add release notes for 4.0.29, 5.0.12 and 5.2.3
197- pkgconfig: fix build with gcc-15
198- poky.conf: bump version for 5.2.4
199- pulseaudio: Add audio group explicitly
200- python3-setuptools: restore build_scripts.executable support
201- ref-manual/variables.rst: expand :term:`IMAGE_OVERHEAD_FACTOR` glossary entry
202- rpm: correct tool path in macros for no usrmerge
203- rpm: keep leading '/' from sed operation
204- runqemu: fix special characters bug
205- rust-target-config: Add has-thread-local option
206- sanity.conf: Update minimum bitbake version to 2.12.1
207- sdk: The main in the C example should return an int
208- systemd-systemctl-native: Install systemd-sysv-install
209- systemd-systemctl-native: Use += instead of :append
210- systemd.bbclass: Make systemd_postinst run as intended
211- vim: upgrade 9.1.1652
212- vulnerabilities: update nvdcve file name
213- yocto-uninative: Update to 4.9 for glibc 2.42 and GCC 15.1
214
215
216Known Issues in Yocto-5.2.4
217~~~~~~~~~~~~~~~~~~~~~~~~~~~
218
219- N/A
220
221
222Contributors to Yocto-5.2.4
223~~~~~~~~~~~~~~~~~~~~~~~~~~~
224
225- Antonin Godard
226- Archana Polampalli
227- Bruce Ashfield
228- Deepak Rathore
229- Haixiao Yan
230- Harish Sadineni
231- Hongxu Jia
232- Jan Vermaete
233- Joao Marcos Costa
234- Joshua Watt
235- Kyungjik Min
236- Lee Chee Yang
237- Libo Chen
238- Markus Kurz
239- Markus Volk
240- Martin Jansa
241- Mathieu Dubois-Briand
242- Michael Halstead
243- Patryk Seregiet
244- Per x Johansson
245- Peter Kjellerstedt
246- Peter Marko
247- Praveen Kumar
248- Ross Burton
249- Siddharth Doshi
250- Soumya Sambu
251- Steve Sakoman
252- Yi Zhao
253- Yogita Urade
254
255
256Repositories / Downloads for Yocto-5.2.4
257~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
258
259poky
260
261- Repository Location: :yocto_git:`/poky`
262- Branch: :yocto_git:`walnascar </poky/log/?h=walnascar>`
263- Tag: :yocto_git:`yocto-5.2.4 </poky/log/?h=yocto-5.2.4>`
264- Git Revision: :yocto_git:`d0b46a6624ec9c61c47270745dd0b2d5abbe6ac1 </poky/commit/?id=d0b46a6624ec9c61c47270745dd0b2d5abbe6ac1>`
265- Release Artefact: poky-d0b46a6624ec9c61c47270745dd0b2d5abbe6ac1
266- sha: b5fa58650f7069c1c001f48aa8eeb12ab78b5f50a414de46df1a196fdc3be8cb
267- Download Locations:
268 https://downloads.yoctoproject.org/releases/yocto/yocto-5.2.4/poky-d0b46a6624ec9c61c47270745dd0b2d5abbe6ac1.tar.bz2
269 https://mirrors.kernel.org/yocto/yocto/yocto-5.2.4/poky-d0b46a6624ec9c61c47270745dd0b2d5abbe6ac1.tar.bz2
270
271openembedded-core
272
273- Repository Location: :oe_git:`/openembedded-core`
274- Branch: :oe_git:`walnascar </openembedded-core/log/?h=walnascar>`
275- Tag: :oe_git:`yocto-5.2.4 </openembedded-core/log/?h=yocto-5.2.4>`
276- Git Revision: :oe_git:`ff1c54df4e7b15df2e2c9fced59d9ad3e92ed565 </openembedded-core/commit/?id=ff1c54df4e7b15df2e2c9fced59d9ad3e92ed565>`
277- Release Artefact: oecore-ff1c54df4e7b15df2e2c9fced59d9ad3e92ed565
278- sha: a348eb7c759cc02c1415d2b506903ac1d5530708c9b47550a4ae8c8d86c75728
279- Download Locations:
280 https://downloads.yoctoproject.org/releases/yocto/yocto-5.2.4/oecore-ff1c54df4e7b15df2e2c9fced59d9ad3e92ed565.tar.bz2
281 https://mirrors.kernel.org/yocto/yocto/yocto-5.2.4/oecore-ff1c54df4e7b15df2e2c9fced59d9ad3e92ed565.tar.bz2
282
283meta-mingw
284
285- Repository Location: :yocto_git:`/meta-mingw`
286- Branch: :yocto_git:`walnascar </meta-mingw/log/?h=walnascar>`
287- Tag: :yocto_git:`yocto-5.2.4 </meta-mingw/log/?h=yocto-5.2.4>`
288- Git Revision: :yocto_git:`edce693e1b8fabd84651aa6c0888aafbcf238577 </meta-mingw/commit/?id=edce693e1b8fabd84651aa6c0888aafbcf238577>`
289- Release Artefact: meta-mingw-edce693e1b8fabd84651aa6c0888aafbcf238577
290- sha: 6cfed41b54f83da91a6cf201ec1c2cd4ac284f642b1268c8fa89d2335ea2bce1
291- Download Locations:
292 https://downloads.yoctoproject.org/releases/yocto/yocto-5.2.4/meta-mingw-edce693e1b8fabd84651aa6c0888aafbcf238577.tar.bz2
293 https://mirrors.kernel.org/yocto/yocto/yocto-5.2.4/meta-mingw-edce693e1b8fabd84651aa6c0888aafbcf238577.tar.bz2
294
295bitbake
296
297- Repository Location: :oe_git:`/bitbake`
298- Branch: :oe_git:`2.12 </bitbake/log/?h=2.12>`
299- Tag: :oe_git:`yocto-5.2.4 </bitbake/log/?h=yocto-5.2.4>`
300- Git Revision: :oe_git:`ac097300921590ed6a814f2c3fa08a59f4ded92d </bitbake/commit/?id=ac097300921590ed6a814f2c3fa08a59f4ded92d>`
301- Release Artefact: bitbake-ac097300921590ed6a814f2c3fa08a59f4ded92d
302- sha: ad8afd956f5378691172317c95bdd1c098d6144a7269975d7d3230707305e88a
303- Download Locations:
304 https://downloads.yoctoproject.org/releases/yocto/yocto-5.2.4/bitbake-ac097300921590ed6a814f2c3fa08a59f4ded92d.tar.bz2
305 https://mirrors.kernel.org/yocto/yocto/yocto-5.2.4/bitbake-ac097300921590ed6a814f2c3fa08a59f4ded92d.tar.bz2
306
307meta-yocto
308
309- Repository Location: :yocto_git:`/meta-yocto`
310- Branch: :yocto_git:`walnascar </meta-yocto/log/?h=walnascar>`
311- Tag: :yocto_git:`yocto-5.2.4 </meta-yocto/log/?h=yocto-5.2.4>`
312- Git Revision: :yocto_git:`0993c45a1f78f302fd40c78a2a1f709daa7a0ae0 </meta-yocto/commit/?id=0993c45a1f78f302fd40c78a2a1f709daa7a0ae0>`
313
314yocto-docs
315
316- Repository Location: :yocto_git:`/yocto-docs`
317- Branch: :yocto_git:`walnascar </yocto-docs/log/?h=walnascar>`
318- Tag: :yocto_git:`yocto-5.2.4 </yocto-docs/log/?h=yocto-5.2.4>`
319- Git Revision: :yocto_git:`29330751c8a2b82b4bd80659d2a0a8bac51afca5 </yocto-docs/commit/?id=29330751c8a2b82b4bd80659d2a0a8bac51afca5>`
320
diff --git a/documentation/migration-guides/release-notes-5.3.rst b/documentation/migration-guides/release-notes-5.3.rst
index 417087e352..5cd875e9b5 100644
--- a/documentation/migration-guides/release-notes-5.3.rst
+++ b/documentation/migration-guides/release-notes-5.3.rst
@@ -11,10 +11,21 @@ Release notes for |yocto-ver| (|yocto-codename|)
11New Features / Enhancements in |yocto-ver| 11New Features / Enhancements in |yocto-ver|
12~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 12~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
13 13
14- Linux kernel XXX, gcc 15, glibc XXX, LLVM XXX, and over XXX other 14- Linux kernel 6.16, gcc 15, glibc 2.42, LLVM 21.1.1, and over 300 other
15 recipe upgrades. 15 recipe upgrades.
16 16
17- Minimum Python version required on the host: XXX. 17- Minimum Python version required on the host: 3.9.
18
19- Host requirements changes:
20
21 - The minimum disk space requirement is now 140Gbytes (previously 90Gbytes).
22
23 - The minimum RAM requirement is now 32Gbytes (previously 8Gbytes).
24
25 - These changes are mainly due to recent additions of the LLVM and other
26 resource heavy recipes. For guidance on how to limit the resources used by
27 the :term:`OpenEmbedded Build System`, see the
28 :doc:`/dev-manual/limiting-resources` guide.
18 29
19- BitBake changes: 30- BitBake changes:
20 31
@@ -36,10 +47,18 @@ New Features / Enhancements in |yocto-ver|
36 - ``az``: Add sanity check to check that :term:`AZ_SAS` starts with ``?`` 47 - ``az``: Add sanity check to check that :term:`AZ_SAS` starts with ``?``
37 to mark the start of the query parameters. 48 to mark the start of the query parameters.
38 49
39 - ``git``: Add the tag to shallow clone tarball name. 50 - ``git``:
51
52 - Add the tag to shallow clone tarball name.
53 - Verify if local clones contains a tag, when the ``tag=`` parameter
54 is used in :term:`SRC_URI`.
55
56 - ``knotty``:
57
58 - Pass failed task logs through the log infrastructure (use
59 ``bb.plain()`` instead of ``print()``).
40 60
41 - ``knotty``: pass failed task logs through the log infrastructure (use 61 - Improve refresh rate of the footer progress bar.
42 ``bb.plain()`` instead of ``print()``)
43 62
44 - Add support for automatically promoting class inherits to deferred 63 - Add support for automatically promoting class inherits to deferred
45 inherits by listing them in the :term:`BB_DEFER_BBCLASSES` variable. 64 inherits by listing them in the :term:`BB_DEFER_BBCLASSES` variable.
@@ -92,6 +111,17 @@ New Features / Enhancements in |yocto-ver|
92 :term:`BitBake` to specify what to profile. Can be "main", "idle" or 111 :term:`BitBake` to specify what to profile. Can be "main", "idle" or
93 "parsing". Split the reports in separate files. 112 "parsing". Split the reports in separate files.
94 113
114 - A "filtering" functionality was added and allows modifying the value of a
115 variable before its value is returned by :term:`BitBake`. The
116 ``setVarFilter`` API can be used for applying the filters, but it is
117 **not** recommended for general use. It was added for internal use in
118 the :term:`OpenEmbedded Build System` in the :ref:`ref-classes-native`
119 class. The list of filters that are allowed are derived from a select
120 list of functions that must be added using a ``filter_proc`` decorator.
121
122 - ``tests/parse``: Add tests for ``include``, ``require`` and
123 ``include_all``.
124
95- Toolchain changes: 125- Toolchain changes:
96 126
97 - The Clang/LLVM toolchain can now be used as part of the build. 127 - The Clang/LLVM toolchain can now be used as part of the build.
@@ -106,6 +136,12 @@ New Features / Enhancements in |yocto-ver|
106 The toolchain is also customizable on a per-recipe basis, using the 136 The toolchain is also customizable on a per-recipe basis, using the
107 :term:`TOOLCHAIN` and :term:`TOOLCHAIN_NATIVE` variables. 137 :term:`TOOLCHAIN` and :term:`TOOLCHAIN_NATIVE` variables.
108 138
139 .. warning::
140
141 The :term:`TOOLCHAIN` should **not** be set globally. For overriding
142 the toolchain globally, use :term:`PREFERRED_TOOLCHAIN_TARGET`,
143 :term:`PREFERRED_TOOLCHAIN_NATIVE` and :term:`PREFERRED_TOOLCHAIN_SDK`.
144
109 - Multiple recipes were pinned to use the GCC/Binutils toolchain as they do 145 - Multiple recipes were pinned to use the GCC/Binutils toolchain as they do
110 not support being built with Clang/LLVM yet. In these recipes the 146 not support being built with Clang/LLVM yet. In these recipes the
111 :term:`TOOLCHAIN` variable is set to "gcc". 147 :term:`TOOLCHAIN` variable is set to "gcc".
@@ -119,14 +155,42 @@ New Features / Enhancements in |yocto-ver|
119 - ``bitbake.conf``: Drop ``lz4`` from :term:`HOSTTOOLS`, as it is not 155 - ``bitbake.conf``: Drop ``lz4`` from :term:`HOSTTOOLS`, as it is not
120 required anymore, and the ``lz4-native`` package is used instead. 156 required anymore, and the ``lz4-native`` package is used instead.
121 157
122 - ``conf/fragments``: add a fragment for the CDN :ref:`sstate-cache 158 - :term:`Configuration Fragments <Configuration Fragment>`:
123 <overview-manual/concepts:shared state cache>` mirror. 159
160 - Add a fragment for the `CDN` :ref:`sstate-cache
161 <overview-manual/concepts:shared state cache>` mirror.
162
163 - Add a ``show-fragments`` sub-command to the
164 :oe_git:`bitbake-config-build </bitbake/tree/bin/bitbake-config-build>`
165 utility, to show the content of fragments from command-line.
124 166
125 - ``default-distrovars``: set an empty default for :term:`LICENSE_PATH`. 167 - ``default-distrovars``: set an empty default for :term:`LICENSE_PATH`.
126 168
127 - The default definition of :term:`UNPACKDIR` is no longer 169 - The default definition of :term:`UNPACKDIR` is no longer
128 ``sources-unpack`` but ``sources``. 170 ``sources-unpack`` but ``sources``.
129 171
172 - The default value for :term:`IMAGE_FSTYPES` (defined in
173 :oe_git:`bitbake.conf </openembedded-core/tree/meta/conf/bitbake.conf>`)
174 is now ``tar.zst`` (previously ``tar.gz``).
175
176 - Remove the ``meta/conf/distro/include/distro_alias.inc`` include file,
177 which associated a recipe name to one or more Distribution package name.
178 This file is not used and maintained anymore.
179
180 - A new configuration file :ref:`structure-build-conf-toolcfg.conf` is now
181 used by :oe_git:`bitbake-config-build </bitbake/tree/bin/bitbake-config-build>`
182 to manage :term:`Configuration Fragments <Configuration Fragment>`.
183
184 - ``bitbake.conf``: add :term:`TMPDIR` to the ``GIT_CEILING_DIRECTORIES``
185 Git variable. This avoids Git trying to find a repository higher than
186 :term:`TMPDIR` in recipes that use the :ref:`structure-build-work-shared`
187 directory for storing their sources. This fixes reproducibility issues.
188
189 - Changes to the ``genericarm64`` machine configuration:
190
191 - Increase the :term:`Initramfs` maximum size.
192 - Install extra Linux firmware packages to fix Linux kernel warnings.
193
130- New variables: 194- New variables:
131 195
132 - The ``VIRTUAL-RUNTIME_dbus`` variable, to allow changing the runtime 196 - The ``VIRTUAL-RUNTIME_dbus`` variable, to allow changing the runtime
@@ -159,6 +223,11 @@ New Features / Enhancements in |yocto-ver|
159 deployed filenames. Users can now override :term:`UBOOT_VERSION` to 223 deployed filenames. Users can now override :term:`UBOOT_VERSION` to
160 changes the output filenames. 224 changes the output filenames.
161 225
226 - The :term:`UBOOT_MAKE_OPTS` variable specifies extra options passed to
227 ``make`` when building U-boot. Extra options can also be passed as the
228 fourth argument of the :term:`UBOOT_CONFIG` variable. See the
229 documentation of :ref:`ref-classes-uboot-config` class for more details.
230
162- Kernel-related changes: 231- Kernel-related changes:
163 232
164 - ``linux/generate-cve-exclusions``: use data from CVEProject instead of 233 - ``linux/generate-cve-exclusions``: use data from CVEProject instead of
@@ -186,6 +255,8 @@ New Features / Enhancements in |yocto-ver|
186 - ``linux-yocto``: when built for RISC-V, enable features in 255 - ``linux-yocto``: when built for RISC-V, enable features in
187 :term:`KERNEL_FEATURES` based on features listed in :term:`TUNE_FEATURES`. 256 :term:`KERNEL_FEATURES` based on features listed in :term:`TUNE_FEATURES`.
188 257
258 - ``perf``: Enable ``coresight`` if enabled in :term:`MACHINE_FEATURES`.
259
189- New core recipes: 260- New core recipes:
190 261
191 - ``python3-pdm``, ``python3-pdm-backend`` and ``python3-pdm-build-locked``, 262 - ``python3-pdm``, ``python3-pdm-backend`` and ``python3-pdm-build-locked``,
@@ -210,6 +281,13 @@ New Features / Enhancements in |yocto-ver|
210 to code blocks in Sphinx. It is part of ``buildtools-docs-tarball`` for later 281 to code blocks in Sphinx. It is part of ``buildtools-docs-tarball`` for later
211 use in the Yocto Project documentation. 282 use in the Yocto Project documentation.
212 283
284 - ``python3-coherent-licensed``: License management tooling for `Coherent
285 System` and skeleton projects. It became a new dependency of
286 ``python3-zipp``.
287
288 - ``gn``: a commonly used build tool to generate `ninja
289 <https://ninja-build.org/>`__ files.
290
213 - LLVM/Clang related recipes: 291 - LLVM/Clang related recipes:
214 292
215 - ``clang``: LLVM based C/C++ compiler. 293 - ``clang``: LLVM based C/C++ compiler.
@@ -225,11 +303,15 @@ New Features / Enhancements in |yocto-ver|
225 - ``llvm-tblgen-native``: LLVM TableGen binaries for the build host, 303 - ``llvm-tblgen-native``: LLVM TableGen binaries for the build host,
226 often used to build LLVM projects. 304 often used to build LLVM projects.
227 305
306 - ``lld``: the LLVM Linker.
307
228 - ``lldb``: LLDB debugger for LLVM projects. 308 - ``lldb``: LLDB debugger for LLVM projects.
229 309
230 - ``llvm-project-source``: canonical git mirror of the LLVM subversion 310 - ``llvm-project-source``: canonical git mirror of the LLVM subversion
231 repository. 311 repository.
232 312
313 - ``llvm``: The LLVM Compiler Infrastructure.
314
233 - ``openmp``: LLVM OpenMP compiler Runtime. 315 - ``openmp``: LLVM OpenMP compiler Runtime.
234 316
235 - ``kernel-signing-keys-native``: this recipe is used in the 317 - ``kernel-signing-keys-native``: this recipe is used in the
@@ -242,6 +324,9 @@ New Features / Enhancements in |yocto-ver|
242 - ``glvnd``, which enables OpenGL Vendor Neutral Dispatch Library 324 - ``glvnd``, which enables OpenGL Vendor Neutral Dispatch Library
243 support when using recipes such as ``mesa``. 325 support when using recipes such as ``mesa``.
244 326
327 - ``opencl``: support for the :wikipedia:`OpenCL (Open Computing Language)
328 <OpenCL>` framework.
329
245- New core classes: 330- New core classes:
246 331
247 - The new :ref:`ref-classes-kernel-fit-image` class replaces the previous 332 - The new :ref:`ref-classes-kernel-fit-image` class replaces the previous
@@ -255,6 +340,10 @@ New Features / Enhancements in |yocto-ver|
255 maintain Go recipes that use a ``BPN-go-mods.inc`` and 340 maintain Go recipes that use a ``BPN-go-mods.inc`` and
256 ``BPN-licenses.inc`` and update these files automatically. 341 ``BPN-licenses.inc`` and update these files automatically.
257 342
343 - The new :ref:`ref-classes-python_pdm` class supports building Python
344 recipes with the `PDM <https://pdm-project.org/>`__ package and dependency
345 manager.
346
258- Architecture-specific changes: 347- Architecture-specific changes:
259 348
260 - Rework the RISC-V :term:`TUNE_FEATURES` to make them based of the RISC-V 349 - Rework the RISC-V :term:`TUNE_FEATURES` to make them based of the RISC-V
@@ -299,6 +388,16 @@ New Features / Enhancements in |yocto-ver|
299 </openembedded-core/tree/meta/conf/machine/include/riscv/README>` for more 388 </openembedded-core/tree/meta/conf/machine/include/riscv/README>` for more
300 information. 389 information.
301 390
391 - Add support for new Arm64 instruction sets, which are represented as files
392 to be included in :term:`MACHINE` configuration in :term:`OpenEmbedded-Core
393 (OE-Core)`. The new configuration files are:
394
395 - :oe_git:`conf/machine/include/arm/arch-armv8-7a.inc </openembedded-core/tree/meta/conf/machine/include/arm/arch-armv8-7a.inc>`
396 - :oe_git:`conf/machine/include/arm/arch-armv8-8a.inc </openembedded-core/tree/meta/conf/machine/include/arm/arch-armv8-8a.inc>`
397 - :oe_git:`conf/machine/include/arm/arch-armv9-1a.inc </openembedded-core/tree/meta/conf/machine/include/arm/arch-armv9-1a.inc>`
398 - :oe_git:`conf/machine/include/arm/arch-armv9-2a.inc </openembedded-core/tree/meta/conf/machine/include/arm/arch-armv9-2a.inc>`
399 - :oe_git:`conf/machine/include/arm/arch-armv9-3a.inc </openembedded-core/tree/meta/conf/machine/include/arm/arch-armv9-3a.inc>`
400
302 - ``arch-mips.inc``: Use ``-EB``/``-EL`` for denoting Endianness. 401 - ``arch-mips.inc``: Use ``-EB``/``-EL`` for denoting Endianness.
303 402
304 - Enable ``riscv32`` as supported arch for ``musl`` systems. 403 - Enable ``riscv32`` as supported arch for ``musl`` systems.
@@ -306,6 +405,15 @@ New Features / Enhancements in |yocto-ver|
306 - Powerpc: Use ``-maltivec`` in compiler flags if ``altivec`` is in 405 - Powerpc: Use ``-maltivec`` in compiler flags if ``altivec`` is in
307 :term:`TUNE_FEATURES`. 406 :term:`TUNE_FEATURES`.
308 407
408 - ``arm``: add a ``nocrypto`` feature to :term:`TUNE_FEATURES` to complement
409 the ``crypto`` feature to explicitly disable cryptographic extensions via
410 `GCC` flags.
411
412 This lead to the creation of two new tunes:
413
414 - ``tune-cortexa72-nocrypto``
415 - ``tune-cortexa53-nocrypto``
416
309- QEMU / ``runqemu`` changes: 417- QEMU / ``runqemu`` changes:
310 418
311 - Refactor :ref:`ref-classes-qemu` functions into library functions (in 419 - Refactor :ref:`ref-classes-qemu` functions into library functions (in
@@ -330,19 +438,40 @@ New Features / Enhancements in |yocto-ver|
330 machine's CPU must also be recent enough to support these instructions 438 machine's CPU must also be recent enough to support these instructions
331 natively. 439 natively.
332 440
333 - ``runqemu`` can now run compressed images with snapshot mode. For example, 441 - ``runqemu``:
334 with ``IMAGE_FSTYPES = "... ext4.zst ..."``, you can run:: 442
443 - The script can now run compressed images with snapshot mode. For
444 example, with :term:`IMAGE_FSTYPES` containing ``ext4.zst``, you can run::
445
446 runqemu snapshot ext4.zst <image-recipe>
335 447
336 runqemu snapshot ext4.zst <image-recipe> 448 - Add support for the ``erofs`` filesystem.
449
450 - The :term:`BitBake` environment is now a requirement, and the script
451 cannot run without a successful call to ``bitbake -e``.
452
453 The script will also raise an error with the ``bitbake`` command is not
454 found.
337 455
338- Documentation changes: 456- Documentation changes:
339 457
458 - Add documentation on :term:`Configuration Fragments <Configuration
459 Fragment>`:
460
461 - :doc:`/ref-manual/fragments`
462 - :doc:`/dev-manual/creating-fragments`
463
340 - Part of :term:`BitBake` internals are now documented at 464 - Part of :term:`BitBake` internals are now documented at
341 :yocto_docs:`/bitbake/bitbake-user-manual/bitbake-user-manual-library-functions.html`. 465 :yocto_docs:`/bitbake/bitbake-user-manual/bitbake-user-manual-library-functions.html`.
342 466
343 - A new :doc:`/dev-manual/limiting-resources` guide was created to help 467 - A new :doc:`/dev-manual/limiting-resources` guide was created to help
344 users limit the host resources used by the :term:`OpenEmbedded Build 468 users limit the resources used by the :term:`OpenEmbedded Build System`.
345 System`. 469
470 - A new :doc:`/dev-manual/hashequivserver` guide was created to help users
471 setting up a :ref:`overview-manual/concepts:Hash Equivalence` server.
472
473 - The QA checks defined in the :term:`OpenEmbedded Build System` were
474 gathered in :doc:`/ref-manual/qa-checks`.
346 475
347- Core library changes: 476- Core library changes:
348 477
@@ -352,6 +481,9 @@ New Features / Enhancements in |yocto-ver|
352 481
353- Go changes: 482- Go changes:
354 483
484 - :ref:`ref-classes-go-mod-update-modules`: Update license finding to use
485 the new ``find_licenses_up`` library function.
486
355- Rust changes: 487- Rust changes:
356 488
357 - ``rust-llvm``: 489 - ``rust-llvm``:
@@ -362,6 +494,9 @@ New Features / Enhancements in |yocto-ver|
362 - Disable the following feature through configuration 494 - Disable the following feature through configuration
363 (:ref:`ref-tasks-configure`): libedit, benchmarks. 495 (:ref:`ref-tasks-configure`): libedit, benchmarks.
364 496
497 - Add the ``has-thread-local`` option to the
498 :ref:`ref-classes-rust-target-config` class.
499
365- Wic Image Creator changes: 500- Wic Image Creator changes:
366 501
367 - After a Python upgrade, WIC plugins containing dashes (``-``) for their 502 - After a Python upgrade, WIC plugins containing dashes (``-``) for their
@@ -387,14 +522,36 @@ New Features / Enhancements in |yocto-ver|
387 :term:`BitBake` variables. This directory is usually found in 522 :term:`BitBake` variables. This directory is usually found in
388 :term:`STAGING_DIR`. 523 :term:`STAGING_DIR`.
389 524
390 - Add the Wic-specific option ``--extra-partiton-space`` to add extra empty 525 - Add the Wic-specific option ``--extra-partition-space`` to add extra empty
391 space after the space filled by the filesystem in the partition. 526 space after the space filled by the filesystem in the partition.
527
528 - The Wic-specific option ``--extra-space`` has a new alias
529 ``--extra-filesystem-space``.
530
531 - ``bootimg_pcbios``: move Syslinux install into separate functions, to make
532 it easier to add new bootloaders.
533
534 The Grub bootloader can now be installed with this Wic plugin.
535
536 - Add the Wic plugin ``extra_partition`` to install files from the
537 :term:`DEPLOY_DIR_IMAGE` directory into an extra non-rootfs partition. See the
538 :term:`IMAGE_EXTRA_PARTITION_FILES` variable for more information.
392 539
393- SDK-related changes: 540- SDK-related changes:
394 541
395 - Include additional information about Meson setting in the SDK environment 542 - Include additional information about Meson setting in the SDK environment
396 setup script (host system, CPU family, etc.). 543 setup script (host system, CPU family, etc.).
397 544
545 - Add Go to :term:`SDK_TOOLCHAIN_LANGS`, except for the following
546 architecture on which this is not supported:
547
548 - RISC-V 32 bits (``rv32``)
549 - PowerPC
550
551 - Image-based SDKs can now include `Zsh` completions by adding the
552 ``zsh-completion-pkgs`` feature to the :term:`IMAGE_FEATURES` variable in
553 the image recipe.
554
398- Testing-related changes: 555- Testing-related changes:
399 556
400 - ``bitbake/tests/fetch``: Add tests for ``gitsm`` with git-lfs. 557 - ``bitbake/tests/fetch``: Add tests for ``gitsm`` with git-lfs.
@@ -402,6 +559,9 @@ New Features / Enhancements in |yocto-ver|
402 - ``bitbake/lib/bb/tests/fetch``: add a test case to ensure Git shallow 559 - ``bitbake/lib/bb/tests/fetch``: add a test case to ensure Git shallow
403 fetch works for tag containing slashes. 560 fetch works for tag containing slashes.
404 561
562 - :ref:`ref-classes-testexport`: capture all tests and data from all layers
563 (instead of the :term:`OpenEmbedded-Core (OE-Core)` layer only).
564
405 - OEQA: 565 - OEQA:
406 566
407 - SDK: 567 - SDK:
@@ -452,8 +612,16 @@ New Features / Enhancements in |yocto-ver|
452 612
453 - ``runqemu``: add new test for booting compressed images. 613 - ``runqemu``: add new test for booting compressed images.
454 614
455 - :ref:`ref-classes-testexport`: capture all tests and data from all layers 615 - General improvements of the parallelization of tests, namely fixing
456 (instead of the :term:`OpenEmbedded-Core (OE-Core)` layer only). 616 some tests that could spawn an unlimited number of threads leading to
617 OOM kills.
618
619 - A new SDK test is now running for Go after ``go`` was added to
620 :term:`SDK_TOOLCHAIN_LANGS`.
621
622 - Commands sent over SSH (using the ``OESSHTarget`` class) will now error
623 when an SSH failure occurs. It is possible to ignore these errors by
624 passing ``ignore_ssh_fails`` when executing a command.
457 625
458- Utility script changes: 626- Utility script changes:
459 627
@@ -465,6 +633,8 @@ New Features / Enhancements in |yocto-ver|
465 patch files *must* include an ``Upstream-Status`` to pass with this 633 patch files *must* include an ``Upstream-Status`` to pass with this
466 script. 634 script.
467 635
636 - Show the :term:`DISTRO` used when running the script.
637
468 - :ref:`ref-classes-yocto-check-layer` class: 638 - :ref:`ref-classes-yocto-check-layer` class:
469 639
470 - Refactor to be extended easily. 640 - Refactor to be extended easily.
@@ -487,7 +657,11 @@ New Features / Enhancements in |yocto-ver|
487 657
488 - ``buildstats-diff``: find last two Buildstats files if none are specified. 658 - ``buildstats-diff``: find last two Buildstats files if none are specified.
489 659
490 - ``pybootchartgui``: visualize ``/proc/net/dev`` network stats in graphs. 660 - ``pybootchartgui``:
661
662 - visualize ``/proc/net/dev`` network stats in graphs.
663
664 - account for network statistics when calculating extents.
491 665
492- Packaging changes: 666- Packaging changes:
493 667
@@ -496,6 +670,19 @@ New Features / Enhancements in |yocto-ver|
496 detailed information on the files used during the compilation and improve 670 detailed information on the files used during the compilation and improve
497 SPDX accuracy. 671 SPDX accuracy.
498 672
673 - When using the ``ipk`` and ``rpm`` package managers, give out more possible
674 reasons about unmatched packages.
675
676 For example::
677
678 E: Package 'catch2' has no installation candidate
679 catch2 is a recipe. Its generated packages are: ['catch2-src', 'catch2-dbg', 'catch2-staticdev', 'catch2-dev', 'catch2-doc']
680 Either specify a generated package or set ALLOW_EMPTY:${PN} = "1" in catch2 recipe
681
682 - ``package.py``: replace all files unconditionally when copying debug
683 sources (passing ``-u`` to the ``cpio`` command in
684 ``copydebugsources()``). This improves reproducibility.
685
499- LLVM related changes: 686- LLVM related changes:
500 687
501 - Like ``gcc-source``, the LLVM project sources are part of ``work-shared`` 688 - Like ``gcc-source``, the LLVM project sources are part of ``work-shared``
@@ -532,14 +719,26 @@ New Features / Enhancements in |yocto-ver|
532 719
533 - Handle workspaces for multiconfig. 720 - Handle workspaces for multiconfig.
534 721
722 - Fix upgrade for recipes with Git submodules.
723
535- Patchtest-related changes: 724- Patchtest-related changes:
536 725
726 - Multiple improvements to the tool's :oe_git:`README
727 </openembedded-core/tree/scripts/patchtest.README>`.
728
729 - Don't match :term:`BitBake` Python expansions as GitHub usernames
730 (``${@...}`` syntax).
731
537- Security changes: 732- Security changes:
538 733
539 - ``openssl``: add FIPS support. This can be enabled through the ``fips`` 734 - ``openssl``: add FIPS support. This can be enabled through the ``fips``
540 :term:`PACKAGECONFIG`. 735 :term:`PACKAGECONFIG`.
541 736
542- :ref:`ref-classes-cve-check` changes: 737- :ref:`ref-classes-cve-check` class changes:
738
739
740 - ``cve-update-db-native``: FKIE: use Secondary metric if there is no
741 Primary metric.
543 742
544- New :term:`PACKAGECONFIG` options for individual recipes: 743- New :term:`PACKAGECONFIG` options for individual recipes:
545 744
@@ -551,13 +750,34 @@ New Features / Enhancements in |yocto-ver|
551 - ``openssl``: ``fips`` 750 - ``openssl``: ``fips``
552 - ``qemu``: ``sdl-image``, ``pixman`` 751 - ``qemu``: ``sdl-image``, ``pixman``
553 - ``wget``: ``pcre2`` 752 - ``wget``: ``pcre2``
554 - ``mesa``: ``asahi``, ``amd``, ``svga``, ``teflon``, ``nouveau`` 753 - ``mesa``: ``asahi``, ``amd``, ``svga``, ``teflon``, ``nouveau``,
754 ``xmlconfig``
755 - ``dbus``: ``traditional-activation``, ``message-bus``
756 - ``cmake``: ``debugger``
757 - ``libcxx``: ``unwind-cross``
758 - ``tiff``: ``lerc``
759 - ``freetype``: ``brotli``
760 - ``gawk``: ``pma-if-64bit``
761 - ``x264``: ``ffmpeg``, ``opencl``
555 762
556- Systemd related changes: 763- Systemd related changes:
557 764
558 - Enable getty generator by default by adding ``serial-getty-generator`` to 765 - Enable getty generator by default by adding ``serial-getty-generator`` to
559 :term:`PACKAGECONFIG`. 766 :term:`PACKAGECONFIG`.
560 767
768 - Now uses the :term:`USE_NLS` variable to enable or disable building
769 translations.
770
771 - Fix deduplicated templates and instance lines in preset files when listing
772 both template and instances in :term:`SYSTEMD_SERVICE`.
773
774 - Stop enabling non-standard MAC policy when using the 'pni-names' feature
775 (part of :term:`DISTRO_FEATURES`). Instead, follow what is provided by
776 upstream systemd.
777
778 - Install ``systemd-sysv-install`` when using the
779 ``systemd-systemctl-native`` recipe.
780
561- :ref:`ref-classes-sanity` class changes: 781- :ref:`ref-classes-sanity` class changes:
562 782
563 - :ref:`ref-classes-insane`: Move test for invalid :term:`PACKAGECONFIG` to 783 - :ref:`ref-classes-insane`: Move test for invalid :term:`PACKAGECONFIG` to
@@ -573,6 +793,9 @@ New Features / Enhancements in |yocto-ver|
573 install ``libstdc++-14-dev`` instead of ``libgcc-14-dev`` to avoid build 793 install ``libstdc++-14-dev`` instead of ``libgcc-14-dev`` to avoid build
574 issues when building :ref:`ref-classes-native` with Clang. 794 issues when building :ref:`ref-classes-native` with Clang.
575 795
796 - Drop the ``var-undefined`` QA check as it was not relevant for the
797 variables it was checking, as those are mandatory by default.
798
576- U-boot related changes: 799- U-boot related changes:
577 800
578 - :ref:`ref-classes-uboot-sign`: Add support for setting firmware property 801 - :ref:`ref-classes-uboot-sign`: Add support for setting firmware property
@@ -586,6 +809,11 @@ New Features / Enhancements in |yocto-ver|
586 variable to automatically set U-boot configuration options (for example 809 variable to automatically set U-boot configuration options (for example
587 ``CONFIG_RISCV_ISA_F``). 810 ``CONFIG_RISCV_ISA_F``).
588 811
812 - Improve the way build directories are split when having multiple
813 configurations listed in :term:`UBOOT_CONFIG`. This fixes an issue where
814 two or more of these configurations were using the same directory for
815 building (because these were using the same defconfig file).
816
589- Miscellaneous changes: 817- Miscellaneous changes:
590 818
591 - ``dropbear``: The ``dropbearkey.service`` can now take extra arguments for 819 - ``dropbear``: The ``dropbearkey.service`` can now take extra arguments for
@@ -645,12 +873,78 @@ New Features / Enhancements in |yocto-ver|
645 - :ref:`ref-classes-externalsrc`: Always ask Git for location of ``.git`` 873 - :ref:`ref-classes-externalsrc`: Always ask Git for location of ``.git``
646 directory (may be different from the default ``${S}/.git``). 874 directory (may be different from the default ``${S}/.git``).
647 875
648 - :ref:`ref-classes-features_check`: Add support for required 876 - :ref:`ref-classes-features_check`: Add support for :term:`REQUIRED_TUNE_FEATURES`.
649 :term:`TUNE_FEATURES`.
650 877
651 - ``openssh``: limit read access to ``sshd_config`` file (set its filemode 878 - ``openssh``: limit read access to ``sshd_config`` file (set its filemode
652 to ``0600``). 879 to ``0600``).
653 880
881 - ``barebox-tools`` now installs the ``rk-usb-loader`` utility.
882
883 - The :ref:`ref-classes-setuptools3_legacy` class now supports the
884 :ref:`qa-check-pep517-backend` QA check.
885
886 - The :ref:`ref-classes-ccache` class now supports using `Ccache` for native
887 recipes when the local build configuration contains::
888
889 ASSUME_PROVIDED += "ccache-native"
890 HOSTTOOLS += "ccache"
891
892 - :ref:`ref-classes-python_pep517`: use ``pyproject-build`` instead of
893 calling the module with ``nativepython3``.
894
895 - ``dbus-glib``: include the binding tools separately into the
896 ``${PN}-tools`` package.
897
898 - ``dbus``: use the :ref:`ref-classes-systemd` class to handle the unit
899 files of D-Bus.
900
901 - ``dpkg``: add :ref:`ptest <test-manual/ptest:testing packages with ptest>`
902 support.
903
904 - ``shared-mime-info``: Now uses the :term:`USE_NLS` variable to enable
905 building translations.
906
907 - ``p11-kit``: Now uses the :term:`USE_NLS` variable to enable building
908 translations.
909
910 - ``babeltrace2``: Enable Python plugins
911
912 - ``initramfs-framework``: mount a temporary filesystem on ``/run`` and move
913 it to the root filesystem directory before calling ``switch_root``.
914
915 - ``python3``: Pass ``PLATFORM_TRIPLET`` explicitly when cross compiling to
916 make the build deterministic instead of letting Python detect the platform
917 triplet (``${HOST_ARCH}-${HOST_OS}``).
918
919 - ``pulseaudio``: Add the ``audio`` group explicitly if
920 ``pulseaudio-server`` is used.
921
922 - ``oe/license_finder``: Add ``find_licenses_up`` function to find licenses
923 upwards until reaching a predefined top directory (as an argument).
924
925 - ``mesa``:
926
927 - Build Mesa's Asahi tools when ``asahi`` is part of the recipe's
928 :term:`PACKAGECONFIG` variable.
929
930 - The ``mesa`` recipe now declares two new :term:`PROVIDES` for Vulkan
931 and OpenCL ICD. These virtual provider are respectively named
932 ``virtual-opencl-icd`` and ``virtual-vulkan-icd``.
933
934 - ``mesa-demos``: split info tools to a separate package ``mesa-demos-info``.
935
936 - ``vte``: skip :ref:`ref-classes-gobject-introspection` with Clang on Arm,
937 as it caused build failures.
938
939 - ``shadow``: Increase the maximum group name length from 24 to 32 (default
940 value provided by upstream recipe, was previously hardcoded to 24).
941
942 - ``udev-extraconf``: Speed up the ``mount.sh`` script by passing the block
943 device of interest to ``blkid`` when getting partition label names.
944
945 - ``piglit``: enable OpenCL support if ``opencl`` is part of the
946 :term:`DISTRO` features.
947
654Known Issues in |yocto-ver| 948Known Issues in |yocto-ver|
655~~~~~~~~~~~~~~~~~~~~~~~~~~~ 949~~~~~~~~~~~~~~~~~~~~~~~~~~~
656 950
diff --git a/documentation/overview-manual/yp-intro.rst b/documentation/overview-manual/yp-intro.rst
index 8fa17b1910..85583567e2 100644
--- a/documentation/overview-manual/yp-intro.rst
+++ b/documentation/overview-manual/yp-intro.rst
@@ -174,11 +174,12 @@ Here are challenges you might encounter when developing using the Yocto Project:
174 changes on the development system within the BitBake environment and 174 changes on the development system within the BitBake environment and
175 then deploying only the updated packages to the target. 175 then deploying only the updated packages to the target.
176 176
177 The Yocto Project :term:`OpenEmbedded Build System` 177 The Yocto Project :term:`OpenEmbedded Build System` produces packages
178 produces packages 178 in standard formats (i.e. RPM, DEB and/or IPK). If you included
179 in standard formats (i.e. RPM, DEB, IPK, and TAR). You can deploy 179 :ref:`runtime package management<dev-manual/packages:using runtime package management>`
180 these packages into the running system on the target by using 180 in your image, you can deploy these packages into the running system on the target
181 utilities on the target such as ``rpm`` or ``ipk``. 181 by using the corresponding utilities on the target such as
182 ``rpm``/``dnf``, ``dpkg``/``apt`` or ``opkg``.
182 183
183- *Initial Build Times Can be Significant:* Long initial build times 184- *Initial Build Times Can be Significant:* Long initial build times
184 are unfortunately unavoidable due to the large number of packages 185 are unfortunately unavoidable due to the large number of packages
diff --git a/documentation/ref-manual/classes.rst b/documentation/ref-manual/classes.rst
index 662121ed9c..a56a2f7198 100644
--- a/documentation/ref-manual/classes.rst
+++ b/documentation/ref-manual/classes.rst
@@ -392,8 +392,19 @@ file for details about how to enable this mechanism in your configuration
392file, how to disable it for specific recipes, and how to share ``ccache`` 392file, how to disable it for specific recipes, and how to share ``ccache``
393files between builds. 393files between builds.
394 394
395However, using the class can lead to unexpected side-effects. Thus, using 395Recipes (including :ref:`ref-classes-native` ones) can make use of the host's
396this class is not recommended. 396``ccache`` binary (via :term:`HOSTTOOLS`) if the following configuration
397statements are provided in a :term:`configuration file`::
398
399 ASSUME_PROVIDED += "ccache-native"
400 HOSTTOOLS += "ccache"
401
402Recipes can also explicitly disable `Ccache` support even when the
403:ref:`ref-classes-ccache` class is enabled, by setting the
404:term:`CCACHE_DISABLE` variable to "1".
405
406Using the :ref:`ref-classes-ccache` class can lead to unexpected side-effects.
407Using this class is not recommended.
397 408
398.. _ref-classes-chrpath: 409.. _ref-classes-chrpath:
399 410
@@ -955,6 +966,14 @@ software that uses the GNU ``gettext`` internationalization and localization
955system. All recipes building software that use ``gettext`` should inherit this 966system. All recipes building software that use ``gettext`` should inherit this
956class. 967class.
957 968
969This class will configure recipes to build translations *unless*:
970
971- the :term:`USE_NLS` variable is set to ``no``, or
972
973- the :term:`INHIBIT_DEFAULT_DEPS` variable is set and the recipe inheriting
974 the :ref:`ref-classes-gettext` class does not also inherit the
975 :ref:`ref-classes-cross-canadian` class.
976
958.. _ref-classes-github-releases: 977.. _ref-classes-github-releases:
959 978
960``github-releases`` 979``github-releases``
@@ -2174,6 +2193,19 @@ meson-python build system.
2174 2193
2175Internally this uses the :ref:`ref-classes-python_pep517` class. 2194Internally this uses the :ref:`ref-classes-python_pep517` class.
2176 2195
2196.. _ref-classes-python_pdm:
2197
2198``python_pdm``
2199=================
2200
2201The :ref:`ref-classes-python_pdm` class adds support for building Python
2202packages with the `PDM <https://pdm-project.org/>`__ package and dependency manager.
2203
2204This class adds ``python3-pdm-backend-native`` to the recipe's build-time
2205dependencies.
2206
2207Internally this uses the :ref:`ref-classes-python_pep517` class.
2208
2177.. _ref-classes-python_pep517: 2209.. _ref-classes-python_pep517:
2178 2210
2179``python_pep517`` 2211``python_pep517``
@@ -2466,6 +2498,25 @@ The :ref:`ref-classes-recipe_sanity` class checks for the presence of any host s
2466recipe prerequisites that might affect the build (e.g. variables that 2498recipe prerequisites that might affect the build (e.g. variables that
2467are set or software that is present). 2499are set or software that is present).
2468 2500
2501.. _ref-classes-relative_symlinks:
2502
2503``relative_symlinks``
2504=====================
2505
2506The :ref:`ref-classes-relative_symlinks` class walks the symbolic links in the
2507:term:`D` directory and replaces links pointing to absolute paths to relative
2508paths. This is occasionally used in some recipes that create wrong symbolic
2509links when their :ref:`ref-classes-native` version is built, and/or would cause
2510breakage in the :ref:`overview-manual/concepts:shared state cache`.
2511
2512For example, if the following symbolic link is found in :term:`D`::
2513
2514 /usr/bin/foo -> /sbin/bar
2515
2516It is replaced by::
2517
2518 /usr/bin/foo -> ../../sbin/bar
2519
2469.. _ref-classes-relocatable: 2520.. _ref-classes-relocatable:
2470 2521
2471``relocatable`` 2522``relocatable``
@@ -2606,6 +2657,19 @@ The :ref:`ref-classes-rust-common` class is an internal class to the
2606:ref:`ref-classes-cargo_common` and :ref:`ref-classes-rust` classes and is not 2657:ref:`ref-classes-cargo_common` and :ref:`ref-classes-rust` classes and is not
2607intended to be used directly. 2658intended to be used directly.
2608 2659
2660.. _ref-classes-rust-target-config:
2661
2662``rust-target-config``
2663======================
2664
2665The :ref:`ref-classes-rust-target-config` class is an internal class to the
2666:ref:`ref-classes-cargo_common` and :ref:`ref-classes-rust` classes and is not
2667intended to be used directly.
2668
2669It is used to generate a JSON specification file from the features listed in
2670:term:`TUNE_FEATURES`, which is used for cross-compiling. The logic is done in a
2671``do_rust_gen_targets`` task.
2672
2609.. _ref-classes-sanity: 2673.. _ref-classes-sanity:
2610 2674
2611``sanity`` 2675``sanity``
@@ -3169,15 +3233,65 @@ variable using the "type" varflag. Here is an example::
3169``uboot-config`` 3233``uboot-config``
3170================ 3234================
3171 3235
3172The :ref:`ref-classes-uboot-config` class provides support for U-Boot configuration for 3236The :ref:`ref-classes-uboot-config` class provides support for configuring one
3173a machine. Specify the machine in your recipe as follows:: 3237or more U-Boot build configurations.
3238
3239There are two ways to configure the recipe for your machine:
3240
3241- Using :term:`UBOOT_CONFIG` variable. For example::
3242
3243 UBOOT_CONFIG ??= "foo bar"
3244 UBOOT_CONFIG[foo] = "config,images,binary,makeopts"
3245 UBOOT_CONFIG[bar] = "config2,images2,binary2,makeopts2"
3246
3247 In this example, all possible configurations are selected (``foo`` and
3248 ``bar``), but it is also possible to build only ``foo`` or ``bar`` by
3249 changing the value of :term:`UBOOT_CONFIG` to include either one or the
3250 other.
3251
3252 Each build configuration is associated to a variable flag definition of
3253 :term:`UBOOT_CONFIG`, that can take up to three comma-separated options
3254 (``config,images,binary``):
3255
3256 - ``config``: defconfig file selected for this build configuration.
3257 These files are found in the source tree's ``configs`` folder of U-Boot.
3258
3259 *This option is mandatory.*
3260
3261 - ``images``: image types to append to the :term:`IMAGE_FSTYPES` variable
3262 for image generation for this build configuration.
3263
3264 This can allow building an extra image format that uses the binary
3265 generated by this build configuration.
3266
3267 This option is not mandatory and can be left empty.
3268
3269 - ``binary``: binary to select as the one to deploy in
3270 :term:`DEPLOY_DIR_IMAGE`. The output of a U-Boot build may be more than
3271 one binary, for example::
3272
3273 u-boot.bin
3274 u-boot-with-spl.bin
3275
3276 Setting the ``binary`` value to ``u-boot-with-spl.bin`` will make this
3277 binary the one deployed in :term:`DEPLOY_DIR_IMAGE`. It is renamed to
3278 include the build configuration name in the process (``foo`` or ``bar`` in
3279 the above example).
3280
3281 This option defaults to :term:`UBOOT_BINARY` if unset.
3282
3283 - ``makeopts``: the additional options passed to ``make`` when configuring
3284 and compiling U-Boot for this configuration entry. The options in this
3285 entry are added before the options in :term:`UBOOT_MAKE_OPTS`.
3174 3286
3175 UBOOT_CONFIG ??= <default> 3287- Or, using the :term:`UBOOT_MACHINE` variable (and its companion variable
3176 UBOOT_CONFIG[foo] = "config,images,binary" 3288 :term:`UBOOT_BINARY`). For example::
3177 3289
3178You can also specify the machine using this method:: 3290 UBOOT_MACHINE = "config"
3291 UBOOT_BINARY = "u-boot.bin"
3179 3292
3180 UBOOT_MACHINE = "config" 3293Using :term:`UBOOT_MACHINE` and :term:`UBOOT_CONFIG` at the same time is not
3294possible.
3181 3295
3182See the :term:`UBOOT_CONFIG` and :term:`UBOOT_MACHINE` variables for additional 3296See the :term:`UBOOT_CONFIG` and :term:`UBOOT_MACHINE` variables for additional
3183information. 3297information.
@@ -3293,22 +3407,51 @@ buildtime via :term:`UKI_FILENAME`.
3293``uninative`` 3407``uninative``
3294============= 3408=============
3295 3409
3296Attempts to isolate the build system from the host distribution's C 3410The :ref:`ref-classes-uninative` class allows binaries to run on systems with
3297library in order to make re-use of native shared state artifacts across 3411older or newer :wikipedia:`Glibc <Glibc>` versions. This means
3298different host distributions practical. With this class enabled, a 3412:ref:`ref-classes-native` recipe :ref:`overview-manual/concepts:shared state
3299tarball containing a pre-built C library is downloaded at the start of 3413cache` can be shared among different host distributions of different versions,
3300the build. In the Poky reference distribution this is enabled by default 3414i.e. the :ref:`overview-manual/concepts:shared state cache` is "universal".
3301through ``meta/conf/distro/include/yocto-uninative.inc``. Other 3415
3302distributions that do not derive from poky can also 3416To allow this to work, the dynamic loader is changed to our own :manpage:`ld.so
3303"``require conf/distro/include/yocto-uninative.inc``" to use this. 3417<ld.so.8>` when binaries are compiled using the
3304Alternatively if you prefer, you can build the uninative-tarball recipe 3418``--dynamic-linker`` option. This means when the binary is executed, it finds
3305yourself, publish the resulting tarball (e.g. via HTTP) and set 3419our own :manpage:`ld.so <ld.so.8>` and that loader has a modified search path
3306``UNINATIVE_URL`` and ``UNINATIVE_CHECKSUM`` appropriately. For an 3420which finds a newer Glibc version.
3307example, see the ``meta/conf/distro/include/yocto-uninative.inc``. 3421
3308 3422The linking of the binaries is not changed at link time since the
3309The :ref:`ref-classes-uninative` class is also used unconditionally by the extensible 3423headers on the system wouldn't match the newer Glibc and this causes
3310SDK. When building the extensible SDK, ``uninative-tarball`` is built 3424obtuse failures. Changing the loader is effectively the same as if the
3311and the resulting tarball is included within the SDK. 3425system had a Glibc upgrade after the binary was compiled, so it is a
3426mechanism supported by upstream.
3427
3428One caveat to this approach is that the uninative Glibc binary must be
3429equal to or newer in version to the versions on all the systems using
3430the common :ref:`overview-manual/concepts:shared state cache`. This is why
3431:ref:`ref-classes-uninative` is regularly changed on the development and stable
3432branches.
3433
3434Another potential issue is static linking: static libraries created on
3435a system with a new Glibc version may have symbols not present in older
3436versions, which would then fail during linking on older systems. This
3437is one reason we don't use static linking for our :ref:`ref-classes-native`
3438binaries.
3439
3440With this class enabled, a tarball containing a pre-built C library is
3441downloaded at the start of the build. In the Poky reference distribution this is
3442enabled by default through :oe_git:`meta/conf/distro/include/yocto-uninative.inc
3443</openembedded-core/tree/meta/conf/distro/include/yocto-uninative.inc>`. Other distributions that do
3444not derive from Poky can also "``require conf/distro/include/yocto-uninative.inc``"
3445to use this. Alternatively if you prefer, you can build the uninative-tarball
3446recipe yourself, publish the resulting tarball (e.g. via HTTP) and set
3447:term:`UNINATIVE_URL` and :term:`UNINATIVE_CHECKSUM` appropriately. For an
3448example, see :oe_git:`meta/conf/distro/include/yocto-uninative.inc
3449</openembedded-core/tree/meta/conf/distro/include/yocto-uninative.inc>`.
3450
3451The :ref:`ref-classes-uninative` class is also used unconditionally by the
3452:doc:`extensible SDK </sdk-manual/extensible>`. When building the extensible
3453SDK, ``uninative-tarball`` is built and the resulting tarball is included within
3454the SDK.
3312 3455
3313.. _ref-classes-update-alternatives: 3456.. _ref-classes-update-alternatives:
3314 3457
diff --git a/documentation/ref-manual/features.rst b/documentation/ref-manual/features.rst
index 2c074ab9c7..40651a4c91 100644
--- a/documentation/ref-manual/features.rst
+++ b/documentation/ref-manual/features.rst
@@ -54,6 +54,11 @@ Project metadata:
54 54
55- *bluetooth:* Hardware has integrated BT 55- *bluetooth:* Hardware has integrated BT
56 56
57- *coresight:* Support for the `Coresight
58 <https://docs.kernel.org/trace/coresight/coresight.html>`__ Linux Kernel
59 feature on Arm processors. This feature depends on the ``opencsd`` recipe
60 which is present in the :yocto_git:`meta-arm </meta-arm>` :term:`layer`.
61
57- *efi:* Support for booting through EFI 62- *efi:* Support for booting through EFI
58 63
59- *ext2:* Hardware HDD or Microdrive 64- *ext2:* Hardware HDD or Microdrive
@@ -180,6 +185,9 @@ metadata, as extra layers can define their own:
180 185
181- *nls:* Include National Language Support (NLS). 186- *nls:* Include National Language Support (NLS).
182 187
188- *opencl:* Include support for the :wikipedia:`OpenCL (Open Computing
189 Language) <OpenCL>` framework.
190
183- *opengl:* Include the Open Graphics Library, which is a 191- *opengl:* Include the Open Graphics Library, which is a
184 cross-language, multi-platform application programming interface used 192 cross-language, multi-platform application programming interface used
185 for rendering two and three-dimensional graphics. 193 for rendering two and three-dimensional graphics.
diff --git a/documentation/ref-manual/qa-checks.rst b/documentation/ref-manual/qa-checks.rst
index 9dfbbff02d..9654cf08e2 100644
--- a/documentation/ref-manual/qa-checks.rst
+++ b/documentation/ref-manual/qa-checks.rst
@@ -983,17 +983,6 @@ message, it indicates that the :ref:`ref-tasks-install` step (or perhaps the bui
983of the variables set up for this (``bindir``, ``sbindir``, etc.), and should be 983of the variables set up for this (``bindir``, ``sbindir``, etc.), and should be
984changed so that it does. 984changed so that it does.
985 985
986.. _qa-check-var-undefined:
987
988``var-undefined``
989-----------------
990
991- ``WORKDIR, DEPLOY_DIR, D, PN and PKGD all must be defined, unable to package [var-undefined]``
992
993 Reports when variables fundamental to packaging (i.e. :term:`WORKDIR`,
994 :term:`DEPLOY_DIR`, :term:`D`, :term:`PN`, and :term:`PKGD`) are undefined
995 during :ref:`ref-tasks-package`.
996
997.. _qa-check-version-going-backwards: 986.. _qa-check-version-going-backwards:
998 987
999``version-going-backwards`` 988``version-going-backwards``
diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index 591c03028c..a80ef364ed 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -1526,6 +1526,11 @@ system and gives an overview of their function and contents.
1526 :term:`CC` 1526 :term:`CC`
1527 The minimal command and arguments used to run the C compiler. 1527 The minimal command and arguments used to run the C compiler.
1528 1528
1529 :term:`CCACHE_DISABLE`
1530 When inheriting the :ref:`ref-classes-ccache` class, the
1531 :term:`CCACHE_DISABLE` variable can be set to "1" in a recipe to disable
1532 `Ccache` support. This is useful when the recipe is known to not support it.
1533
1529 :term:`CCLD` 1534 :term:`CCLD`
1530 The minimal command and arguments used to run the linker when the C 1535 The minimal command and arguments used to run the linker when the C
1531 compiler is being used as the linker. 1536 compiler is being used as the linker.
@@ -3956,6 +3961,70 @@ system and gives an overview of their function and contents.
3956 material for Wic is located in the 3961 material for Wic is located in the
3957 ":doc:`/ref-manual/kickstart`" chapter. 3962 ":doc:`/ref-manual/kickstart`" chapter.
3958 3963
3964 :term:`IMAGE_EXTRA_PARTITION_FILES`
3965 A space-separated list of files installed into the extra partition(s)
3966 when preparing an image using the Wic tool with the
3967 ``extra_partition`` source plugin. By default,
3968 the files are
3969 installed under the same name as the source files. To change the
3970 installed name, separate it from the original name with a semi-colon
3971 (;). Source files need to be located in
3972 :term:`DEPLOY_DIR_IMAGE`. Here is an
3973 example::
3974
3975 IMAGE_EXTRA_PARTITION_FILES = "foobar file.conf;config"
3976
3977 In the above example, the file ``foobar`` is installed with its original name
3978 ``foobar``, while the file ``file.conf`` is installed and renamed to ``config``.
3979
3980 Alternatively, source files can be picked up using a glob pattern.
3981 However, hidden files are ignored, and the pattern is non-recursive
3982 (subdirectories are ignored).
3983 The destination file will have the same name as the base
3984 name of the source file path. To install files into a renamed directory
3985 within the target location, pass its name after a semi-colon (;).
3986 Here are two examples::
3987
3988 IMAGE_EXTRA_PARTITION_FILES = "foo/*"
3989 IMAGE_EXTRA_PARTITION_FILES = "foo/*;bar/"
3990
3991 The first line in this example
3992 installs all files from ``foo`` directory
3993 into the root of the target partition. The second line in this example installs
3994 the same files into a ``bar`` directory within the target partition.
3995 The ``bar/`` directory is automatically created if it does not exist.
3996
3997 You can also specify the target by label, UUID or partition name if multiple
3998 extra partitions coexist. Let's take the following example. This would be
3999 the WKS file for the image currently being built::
4000
4001 part --source extra_partition --fstype=ext4 --label foo
4002 part --source extra_partition --fstype=ext4 --uuid e7d0824e-cda3-4bed-9f54-9ef5312d105d
4003 part --source extra_partition --fstype=ext4 --part-name config
4004
4005 And the following configuration::
4006
4007 IMAGE_EXTRA_PARTITION_FILES_label-foo = "foo/*"
4008 IMAGE_EXTRA_PARTITION_FILES_uuid-e7d0824e-cda3-4bed-9f54-9ef5312d105d = "foo/*;bar/"
4009 IMAGE_EXTRA_PARTITION_FILES_part-name-config = "config"
4010
4011 Then:
4012
4013 - The partition labeled "foo" would get all files from the ``foo``
4014 directory.
4015
4016 - The partition whose UUID is "e7d0824e-cda3-4bed-9f54-9ef5312d105d"
4017 would get all files from the ``foo`` directory, installed into a
4018 ``bar`` directory.
4019
4020 - The partition named "config" would get the file ``config``.
4021
4022 You can find information on how to use the Wic tool in the
4023 ":ref:`dev-manual/wic:creating partitioned images using wic`"
4024 section of the Yocto Project Development Tasks Manual. Reference
4025 material for Wic is located in the
4026 ":doc:`/ref-manual/kickstart`" chapter.
4027
3959 :term:`IMAGE_FEATURES` 4028 :term:`IMAGE_FEATURES`
3960 The primary list of features to include in an image. Typically, you 4029 The primary list of features to include in an image. Typically, you
3961 configure this variable in an image recipe. Although you can use this 4030 configure this variable in an image recipe. Although you can use this
@@ -5454,7 +5523,7 @@ system and gives an overview of their function and contents.
5454 information on how this variable is used. 5523 information on how this variable is used.
5455 5524
5456 :term:`LAYERDEPENDS` 5525 :term:`LAYERDEPENDS`
5457 Lists the layers, separated by spaces, on which this recipe depends. 5526 Lists the layers, separated by spaces, on which this layer depends.
5458 Optionally, you can specify a specific layer version for a dependency 5527 Optionally, you can specify a specific layer version for a dependency
5459 by adding it to the end of the layer name. Here is an example:: 5528 by adding it to the end of the layer name. Here is an example::
5460 5529
@@ -7871,6 +7940,16 @@ system and gives an overview of their function and contents.
7871 :term:`REPODIR` 7940 :term:`REPODIR`
7872 See :term:`bitbake:REPODIR` in the BitBake manual. 7941 See :term:`bitbake:REPODIR` in the BitBake manual.
7873 7942
7943 :term:`REQUIRED_COMBINED_FEATURES`
7944 When inheriting the :ref:`ref-classes-features_check` class, this variable
7945 identifies combined features (the intersection of :term:`MACHINE_FEATURES`
7946 and :term:`DISTRO_FEATURES`) that must exist in the current configuration
7947 in order for the :term:`OpenEmbedded Build System` to build the recipe. In
7948 other words, if the :term:`REQUIRED_COMBINED_FEATURES` variable lists a
7949 feature that does not appear in :term:`COMBINED_FEATURES` within the
7950 current configuration, then the recipe will be skipped, and if the build
7951 system attempts to build the recipe then an error will be triggered.
7952
7874 :term:`REQUIRED_DISTRO_FEATURES` 7953 :term:`REQUIRED_DISTRO_FEATURES`
7875 When inheriting the :ref:`ref-classes-features_check` 7954 When inheriting the :ref:`ref-classes-features_check`
7876 class, this variable identifies distribution features that must exist 7955 class, this variable identifies distribution features that must exist
@@ -7881,6 +7960,41 @@ system and gives an overview of their function and contents.
7881 the recipe will be skipped, and if the build system attempts to build 7960 the recipe will be skipped, and if the build system attempts to build
7882 the recipe then an error will be triggered. 7961 the recipe then an error will be triggered.
7883 7962
7963 :term:`REQUIRED_IMAGE_FEATURES`
7964 When inheriting the :ref:`ref-classes-features_check` class, this variable
7965 identifies image features that must exist in the current
7966 configuration in order for the :term:`OpenEmbedded Build System` to build
7967 the recipe. In other words, if the :term:`REQUIRED_IMAGE_FEATURES` variable
7968 lists a feature that does not appear in :term:`IMAGE_FEATURES` within the
7969 current configuration, then the recipe will be skipped, and if the build
7970 system attempts to build the recipe then an error will be triggered.
7971
7972 Compared to other ``REQUIRED_*_FEATURES`` variables, the
7973 :term:`REQUIRED_IMAGE_FEATURES` varible only targets image recipes, as the
7974 :term:`IMAGE_FEATURES` variable is handled by the :ref:`ref-classes-core-image`
7975 class). However, the :term:`REQUIRED_IMAGE_FEATURES` varible can also be
7976 set from a :term:`Configuration File`, such as a distro
7977 configuration file, if the list of required image features should apply to
7978 all images using this :term:`DISTRO`.
7979
7980 :term:`REQUIRED_MACHINE_FEATURES`
7981 When inheriting the :ref:`ref-classes-features_check` class, this variable
7982 identifies :term:`MACHINE_FEATURES` that must exist in the current
7983 configuration in order for the :term:`OpenEmbedded Build System` to build
7984 the recipe. In other words, if the :term:`REQUIRED_MACHINE_FEATURES` variable
7985 lists a feature that does not appear in :term:`MACHINE_FEATURES` within the
7986 current configuration, then the recipe will be skipped, and if the build
7987 system attempts to build the recipe then an error will be triggered.
7988
7989 :term:`REQUIRED_TUNE_FEATURES`
7990 When inheriting the :ref:`ref-classes-features_check` class, this variable
7991 identifies tune features that must exist in the current configuration in
7992 order for the :term:`OpenEmbedded Build System` to build the recipe. In
7993 other words, if the :term:`REQUIRED_TUNE_FEATURES` variable lists a
7994 feature that does not appear in :term:`TUNE_FEATURES` within the current
7995 configuration, then the recipe will be skipped, and if the build system
7996 attempts to build the recipe then an error will be triggered.
7997
7884 :term:`REQUIRED_VERSION` 7998 :term:`REQUIRED_VERSION`
7885 If there are multiple versions of a recipe available, this variable 7999 If there are multiple versions of a recipe available, this variable
7886 determines which version should be given preference. 8000 determines which version should be given preference.
@@ -10792,6 +10906,12 @@ system and gives an overview of their function and contents.
10792 Please see the "Selection of Processor Architecture and Board Type" 10906 Please see the "Selection of Processor Architecture and Board Type"
10793 section in the U-Boot README for valid values for this variable. 10907 section in the U-Boot README for valid values for this variable.
10794 10908
10909 :term:`UBOOT_MAKE_OPTS`
10910 The :term:`UBOOT_MAKE_OPTS` variable can be used to pass extra options to
10911 ``make`` when U-Boot is configured and compiled.
10912
10913 See the :ref:`ref-classes-uboot-config` class for more information.
10914
10795 :term:`UBOOT_MAKE_TARGET` 10915 :term:`UBOOT_MAKE_TARGET`
10796 Specifies the target called in the ``Makefile``. The default target 10916 Specifies the target called in the ``Makefile``. The default target
10797 is "all". 10917 is "all".
@@ -10914,6 +11034,22 @@ system and gives an overview of their function and contents.
10914 `Unified Kernel Image (UKI) <https://uapi-group.org/specifications/specs/unified_kernel_image/>`__. 11034 `Unified Kernel Image (UKI) <https://uapi-group.org/specifications/specs/unified_kernel_image/>`__.
10915 Defaults to ``ukify build``. 11035 Defaults to ``ukify build``.
10916 11036
11037 :term:`UNINATIVE_CHECKSUM`
11038 When inheriting the :ref:`ref-classes-uninative` class, the
11039 :term:`UNINATIVE_CHECKSUM` variable flags contain the checksums of the
11040 uninative tarball as specified by the :term:`UNINATIVE_URL` variable.
11041 There should be one checksum per tarballs published at
11042 :term:`UNINATIVE_URL`, which match architectures. For example::
11043
11044 UNINATIVE_CHECKSUM[aarch64] ?= "812045d826b7fda88944055e8526b95a5a9440bfef608d5b53fd52faab49bf85"
11045 UNINATIVE_CHECKSUM[i686] ?= "5cc28efd0c15a75de4bcb147c6cce65f1c1c9d442173a220f08427f40a3ffa09"
11046 UNINATIVE_CHECKSUM[x86_64] ?= "4c03d1ed2b7b4e823aca4a1a23d8f2e322f1770fc10e859adcede5777aff4f3a"
11047
11048 :term:`UNINATIVE_URL`
11049 When inheriting the :ref:`ref-classes-uninative` class, the
11050 :term:`UNINATIVE_URL` variable contains the URL where the uninative
11051 tarballs are published.
11052
10917 :term:`UNKNOWN_CONFIGURE_OPT_IGNORE` 11053 :term:`UNKNOWN_CONFIGURE_OPT_IGNORE`
10918 Specifies a list of options that, if reported by the configure script 11054 Specifies a list of options that, if reported by the configure script
10919 as being invalid, should not generate a warning during the 11055 as being invalid, should not generate a warning during the
@@ -10933,7 +11069,7 @@ system and gives an overview of their function and contents.
10933 11069
10934 :term:`UNPACKDIR` 11070 :term:`UNPACKDIR`
10935 This variable, used by the :ref:`ref-classes-base` class, 11071 This variable, used by the :ref:`ref-classes-base` class,
10936 specifies where fetches sources should be unpacked by the 11072 specifies where fetched sources should be unpacked by the
10937 :ref:`ref-tasks-unpack` task. 11073 :ref:`ref-tasks-unpack` task.
10938 11074
10939 :term:`UPDATERCPN` 11075 :term:`UPDATERCPN`
@@ -11009,6 +11145,18 @@ system and gives an overview of their function and contents.
11009 the Yocto Project Development Tasks Manual for information on how to 11145 the Yocto Project Development Tasks Manual for information on how to
11010 use this variable. 11146 use this variable.
11011 11147
11148 :term:`USE_NLS`
11149 Determine if language translations should be built for recipes that can
11150 build them. This variable can be equal to:
11151
11152 - ``yes``: translations are enabled.
11153 - ``no``: translation are disabled.
11154
11155 Recipes can use the value of this variable to enable language
11156 translations in their build. Classes such as :ref:`ref-classes-gettext`
11157 use the value of this variable to enable :wikipedia:`Gettext <Gettext>`
11158 support.
11159
11012 :term:`USE_VT` 11160 :term:`USE_VT`
11013 When using 11161 When using
11014 :ref:`SysVinit <dev-manual/new-recipe:enabling system services>`, 11162 :ref:`SysVinit <dev-manual/new-recipe:enabling system services>`,
diff --git a/documentation/test-manual/reproducible-builds.rst b/documentation/test-manual/reproducible-builds.rst
index b913aa4eaf..336bb7f26a 100644
--- a/documentation/test-manual/reproducible-builds.rst
+++ b/documentation/test-manual/reproducible-builds.rst
@@ -113,7 +113,7 @@ If ``OEQA_DEBUGGING_SAVED_OUTPUT`` is set, any differing packages will be saved
113here. The test is also able to run the ``diffoscope`` command on the output to 113here. The test is also able to run the ``diffoscope`` command on the output to
114generate HTML files showing the differences between the packages, to aid 114generate HTML files showing the differences between the packages, to aid
115debugging. On the Autobuilder, these appear under 115debugging. On the Autobuilder, these appear under
116https://autobuilder.yocto.io/pub/repro-fail/ in the form ``oe-reproducible + 116https://valkyrie.yocto.io/pub/repro-fail/ in the form ``oe-reproducible +
117<date> + <random ID>``, e.g. ``oe-reproducible-20200202-1lm8o1th``. 117<date> + <random ID>``, e.g. ``oe-reproducible-20200202-1lm8o1th``.
118 118
119The project's current reproducibility status can be seen at 119The project's current reproducibility status can be seen at
diff --git a/documentation/test-manual/test-process.rst b/documentation/test-manual/test-process.rst
index 945b56830f..00215385bb 100644
--- a/documentation/test-manual/test-process.rst
+++ b/documentation/test-manual/test-process.rst
@@ -69,7 +69,7 @@ box to "generate an email to QA" is also checked.
69When the build completes, an email is sent out using the ``send-qa-email`` 69When the build completes, an email is sent out using the ``send-qa-email``
70script in the :yocto_git:`yocto-autobuilder-helper </yocto-autobuilder-helper>` 70script in the :yocto_git:`yocto-autobuilder-helper </yocto-autobuilder-helper>`
71repository to the list of people configured for that release. Release builds 71repository to the list of people configured for that release. Release builds
72are placed into a directory in https://autobuilder.yocto.io/pub/releases on the 72are placed into a directory in https://valkyrie.yocto.io/pub/releases on the
73Autobuilder which is included in the email. The process from here is 73Autobuilder which is included in the email. The process from here is
74more manual and control is effectively passed to release engineering. 74more manual and control is effectively passed to release engineering.
75The next steps include: 75The next steps include:
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-10-30 21:41:53 +0000