dev manual, CH 3: update code snippets to be more current
PATCH 1/1 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.
Signed-off-by Robert P. J. Day <[email protected]>
---
documentation/dev-manual/layers.rst +17 -11
@@ -80,7 +80,7 @@ Follow these general steps to create your layer without using tools: BBFILE_PATTERN_yoctobsp = "^${LAYERDIR}/" BBFILE_PRIORITY_yoctobsp = "5" LAYERVERSION_yoctobsp = "4" - LAYERSERIES_COMPAT_yoctobsp = "dunfell" + LAYERSERIES_COMPAT_yoctobsp = "walnascar" 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 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 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
@@ -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 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 ``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
@@ -504,10 +504,11 @@ the "meta" layer at ``meta/recipes-bsp/formfactor``:: SECTION = "base" LICENSE = "MIT" LIC_FILES_CHKSUM = "file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420" - PR = "r45" SRC_URI = "file://config file://machconfig" - S = "${WORKDIR}" + + S = "${WORKDIR}/sources" + UNPACKDIR = "${S}" PACKAGE_ARCH = "${MACHINE_ARCH}" INHIBIT_DEFAULT_DEPS = "1"
@@ -582,11 +583,11 @@ Directory`. Here is the main ``xserver-xf86-config`` recipe, which is named SECTION = "x11/base" LICENSE = "MIT" LIC_FILES_CHKSUM = "file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420" - PR = "r33" SRC_URI = "file://xorg.conf" + SRC_URI:append:qemuall = " file://noblank.conf" - S = "${WORKDIR}" + S = "${UNPACKDIR}" CONFFILES:${PN} = "${sysconfdir}/X11/xorg.conf"
@@ -594,10 +595,15 @@ Directory`. Here is the main ``xserver-xf86-config`` recipe, which is named ALLOW_EMPTY:${PN} = "1" do_install () { - if test -s ${WORKDIR}/xorg.conf; then - install -d ${D}/${sysconfdir}/X11 - install -m 0644 ${WORKDIR}/xorg.conf ${D}/${sysconfdir}/X11/ - fi + if test -s ${S}/xorg.conf; then + install -d ${D}/${sysconfdir}/X11 + install -m 0644 ${S}/xorg.conf ${D}/${sysconfdir}/X11/ + fi + + if test -s ${S}/noblank.conf; then + install -d ${D}/${sysconfdir}/X11/xorg.conf.d + install -m 0644 ${S}/noblank.conf ${D}/${sysconfdir}/X11/xorg.conf.d/ + fi } Here is the append file, which is named ``xserver-xf86-config_%.bbappend``
Quoted 40 lines · Robert P. J. Day
Nothing major, just copy-and-paste from master branch to replace aging code examples, and a little grammmar cleanup.
Signed-off-by Robert P. J. Day <[email protected]>---
documentation/dev-manual/layers.rst +3
-3@@ -80,7 +80,7 @@ Follow these general steps to create your layer without using tools: BBFILE_PATTERN_yoctobsp = "^${LAYERDIR}/" BBFILE_PRIORITY_yoctobsp = "5" LAYERVERSION_yoctobsp = "4" - LAYERSERIES_COMPAT_yoctobsp = "dunfell" + LAYERSERIES_COMPAT_yoctobsp = "walnascar" 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 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 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@@ -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 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 ``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
documentation/dev-manual/layers.rst the "meta" layer at ``meta/recipes-bsp/formfactor``:: · line 511
Quoted 10 lines
documentation/dev-manual/layers.rst +3
-2@@ -504,10 +504,11 @@ the "meta" layer at ``meta/recipes-bsp/formfactor``:: SECTION = "base" LICENSE = "MIT" LIC_FILES_CHKSUM = "file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420" - PR = "r45" SRC_URI = "file://config file://machconfig" - S = "${WORKDIR}" + + S = "${WORKDIR}/sources" + UNPACKDIR = "${S}"
It's now only:
S = "${UNPACKDIR}"Was updated on June 16th. Can you refresh your patch?
Thanks,
Antonin
Signature · 3 lines
Antonin Godard, Bootlin Embedded Linux and Kernel engineering https://bootlin.com