dev manual, CH 3: update code snippets to be more current

Nothing major, just copy-and-paste from master branch to replace aging
code examples, and a little grammmar cleanup.

(From yocto-docs rev: 74057a1ffd682754e81f5f7fbde9f233e14a0d00)

Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Robert P. J. Day 2025-06-20 09:07:40 -04:00 committed by Richard Purdie
parent 06595cf590
commit 034a6278ce

View File

@ -80,7 +80,7 @@ Follow these general steps to create your layer without using tools:
BBFILE_PATTERN_yoctobsp = "^${LAYERDIR}/" BBFILE_PATTERN_yoctobsp = "^${LAYERDIR}/"
BBFILE_PRIORITY_yoctobsp = "5" BBFILE_PRIORITY_yoctobsp = "5"
LAYERVERSION_yoctobsp = "4" LAYERVERSION_yoctobsp = "4"
LAYERSERIES_COMPAT_yoctobsp = "dunfell" LAYERSERIES_COMPAT_yoctobsp = "walnascar"
Here is an explanation of the layer configuration file: Here is an explanation of the layer configuration file:
@ -306,7 +306,7 @@ The Yocto Project Compatibility Program consists of a layer application
process that requests permission to use the Yocto Project Compatibility process that requests permission to use the Yocto Project Compatibility
Logo for your layer and application. The process consists of two parts: Logo for your layer and application. The process consists of two parts:
#. Successfully passing a script (``yocto-check-layer``) that when run #. Successfully passing a script (``yocto-check-layer``) that, when run
against your layer, tests it against constraints based on experiences against your layer, tests it against constraints based on experiences
of how layers have worked in the real world and where pitfalls have of how layers have worked in the real world and where pitfalls have
been found. Getting a "PASS" result from the script is required for been found. Getting a "PASS" result from the script is required for
@ -478,7 +478,7 @@ name. To handle these errors, the best practice is to rename the ``.bbappend``
to match the original recipe version. This also gives you the opportunity to see to match the original recipe version. This also gives you the opportunity to see
if the ``.bbappend`` is still relevant for the new version of the recipe. if the ``.bbappend`` is still relevant for the new version of the recipe.
Another method it to use the character ``%`` in the ``.bbappend`` filename. For Another method is to use the character ``%`` in the ``.bbappend`` filename. For
example, to append information to every ``6.*`` minor versions of the recipe example, to append information to every ``6.*`` minor versions of the recipe
``someapp``, the ``someapp_6.%.bbappend`` file can be created. This way, an ``someapp``, the ``someapp_6.%.bbappend`` file can be created. This way, an
error will only be triggered if the ``someapp`` recipe has a major version error will only be triggered if the ``someapp`` recipe has a major version
@ -504,7 +504,6 @@ the "meta" layer at ``meta/recipes-bsp/formfactor``::
SECTION = "base" SECTION = "base"
LICENSE = "MIT" LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420" LIC_FILES_CHKSUM = "file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
PR = "r45"
SRC_URI = "file://config file://machconfig" SRC_URI = "file://config file://machconfig"
S = "${UNPACKDIR}" S = "${UNPACKDIR}"
@ -582,7 +581,6 @@ Directory`. Here is the main ``xserver-xf86-config`` recipe, which is named
SECTION = "x11/base" SECTION = "x11/base"
LICENSE = "MIT" LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420" LIC_FILES_CHKSUM = "file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
PR = "r33"
SRC_URI = "file://xorg.conf" SRC_URI = "file://xorg.conf"