mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-07-07 05:14:19 +02:00
Code Issues Packages Projects Releases Wiki Activity

dev-manual: drop "PREFERRED_VERSION" from x86-base.inc snippet

Browse Source 
The machine include file "x86-base.inc" no longer includes the line
setting the PREFERRED VERSION -- that setting was removed in commit
298fa078fab58b64246376ffd70ad6a0c7589876 on Oct 1, 2023:

    qemux86/qemuarm: Drop kernel version overrides

    Drop the version overrides for the kernel for the x86 and arm machines
    so we can go back to following the distro versions. The reasons for
    these versions is mostly historical at this point as the issues were
    resolved.

(From yocto-docs rev: 5185c770c30f1041ae1f14290e75f5cc8cfe690d)

Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
(cherry picked from commit a70ce32d8e314afa833079e17757dc9b19590c56)
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Paul Barker <paul@pbarker.dev>
This commit is contained in:
Robert P. J. Day
2026-06-09 10:08:36 -04:00
committed by Paul Barker
parent 4ac62a70a3
commit baa014ae15
1 changed files with 2 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
documentation/dev-manual/new-recipe.rst
View File

@@ -976,11 +976,10 @@ kernel recipe you want by using the :term:`PREFERRED_PROVIDER` variable. As
an example, consider the :yocto_git:`x86-base.inc
</poky/tree/meta/conf/machine/include/x86/x86-base.inc>` include file, which is a
machine (i.e. :term:`MACHINE`) configuration file. This include file is the
reason all x86-based machines use the ``linux-yocto`` kernel. Here are the
relevant lines from the include file::
reason all x86-based machines use the ``linux-yocto`` kernel. Here is the
relevant line from that include file::
PREFERRED_PROVIDER_virtual/kernel ??= "linux-yocto"
PREFERRED_VERSION_linux-yocto ??= "4.15%"
When you use a virtual provider, you do not have to "hard code" a recipe
name as a build dependency. You can use the