summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--documentation/dev-manual/common-tasks.rst80
-rw-r--r--documentation/kernel-dev/advanced.rst2
-rw-r--r--documentation/kernel-dev/common.rst10
-rw-r--r--documentation/kernel-dev/faq.rst2
-rw-r--r--documentation/overview-manual/concepts.rst4
-rw-r--r--documentation/overview-manual/yp-intro.rst2
-rw-r--r--documentation/ref-manual/classes.rst8
-rw-r--r--documentation/ref-manual/qa-checks.rst16
-rw-r--r--documentation/ref-manual/variables.rst52
-rw-r--r--documentation/sdk-manual/appendix-customizing.rst6
-rw-r--r--documentation/sdk-manual/extensible.rst2
-rw-r--r--documentation/test-manual/reproducible-builds.rst2
12 files changed, 93 insertions, 93 deletions
diff --git a/documentation/dev-manual/common-tasks.rst b/documentation/dev-manual/common-tasks.rst
index 7dcb8769d8..34e978dde1 100644
--- a/documentation/dev-manual/common-tasks.rst
+++ b/documentation/dev-manual/common-tasks.rst
@@ -207,13 +207,13 @@ following list:
207 To make sure your changes apply only when building machine "one", 207 To make sure your changes apply only when building machine "one",
208 use a machine override with the :term:`DEPENDS` statement:: 208 use a machine override with the :term:`DEPENDS` statement::
209 209
210 DEPENDS_one = "foo" 210 DEPENDS:one = "foo"
211 211
212 You should follow the same strategy when using ``_append`` 212 You should follow the same strategy when using ``:append``
213 and ``_prepend`` operations:: 213 and ``:prepend`` operations::
214 214
215 DEPENDS:append_one = " foo" 215 DEPENDS:append:one = " foo"
216 DEPENDS:prepend_one = "foo " 216 DEPENDS:prepend:one = "foo "
217 217
218 As an actual example, here's a 218 As an actual example, here's a
219 snippet from the generic kernel include file ``linux-yocto.inc``, 219 snippet from the generic kernel include file ``linux-yocto.inc``,
@@ -236,8 +236,8 @@ following list:
236 236
237 .. note:: 237 .. note::
238 238
239 Avoiding "+=" and "=+" and using machine-specific ``_append`` 239 Avoiding "+=" and "=+" and using machine-specific ``:append``
240 and ``_prepend`` operations is recommended as well. 240 and ``:prepend`` operations is recommended as well.
241 241
242 - *Place Machine-Specific Files in Machine-Specific Locations:* When 242 - *Place Machine-Specific Files in Machine-Specific Locations:* When
243 you have a base recipe, such as ``base-files.bb``, that contains a 243 you have a base recipe, such as ``base-files.bb``, that contains a
@@ -537,7 +537,7 @@ important as it ensures that items in the list remain colon-separated.
537.. note:: 537.. note::
538 538
539 BitBake automatically defines the :term:`THISDIR` variable. You should 539 BitBake automatically defines the :term:`THISDIR` variable. You should
540 never set this variable yourself. Using "_prepend" as part of the 540 never set this variable yourself. Using ":prepend" as part of the
541 :term:`FILESEXTRAPATHS` ensures your path will be searched prior to other 541 :term:`FILESEXTRAPATHS` ensures your path will be searched prior to other
542 paths in the final list. 542 paths in the final list.
543 543
@@ -830,23 +830,23 @@ variable changes are in effect for every build and consequently affect
830all images, which might not be what you require. 830all images, which might not be what you require.
831 831
832To add a package to your image using the local configuration file, use 832To add a package to your image using the local configuration file, use
833the :term:`IMAGE_INSTALL` variable with the ``_append`` operator:: 833the :term:`IMAGE_INSTALL` variable with the ``:append`` operator::
834 834
835 IMAGE_INSTALL:append = " strace" 835 IMAGE_INSTALL:append = " strace"
836 836
837Use of the syntax is important - 837Use of the syntax is important -
838specifically, the space between the quote and the package name, which is 838specifically, the space between the quote and the package name, which is
839``strace`` in this example. This space is required since the ``_append`` 839``strace`` in this example. This space is required since the ``:append``
840operator does not add the space. 840operator does not add the space.
841 841
842Furthermore, you must use ``_append`` instead of the ``+=`` operator if 842Furthermore, you must use ``:append`` instead of the ``+=`` operator if
843you want to avoid ordering issues. The reason for this is because doing 843you want to avoid ordering issues. The reason for this is because doing
844so unconditionally appends to the variable and avoids ordering problems 844so unconditionally appends to the variable and avoids ordering problems
845due to the variable being set in image recipes and ``.bbclass`` files 845due to the variable being set in image recipes and ``.bbclass`` files
846with operators like ``?=``. Using ``_append`` ensures the operation 846with operators like ``?=``. Using ``:append`` ensures the operation
847takes effect. 847takes effect.
848 848
849As shown in its simplest use, ``IMAGE_INSTALL_append`` affects all 849As shown in its simplest use, ``IMAGE_INSTALL:append`` affects all
850images. It is possible to extend the syntax so that the variable applies 850images. It is possible to extend the syntax so that the variable applies
851to a specific image only. Here is an example:: 851to a specific image only. Here is an example::
852 852
@@ -1544,8 +1544,8 @@ package for a recipe has the same name as the recipe, and the recipe's
1544name can be found through the 1544name can be found through the
1545``${``\ :term:`PN`\ ``}`` variable, then 1545``${``\ :term:`PN`\ ``}`` variable, then
1546you specify the dependencies for the main package by setting 1546you specify the dependencies for the main package by setting
1547``RDEPENDS_${PN}``. If the package were named ``${PN}-tools``, then you 1547``RDEPENDS:${PN}``. If the package were named ``${PN}-tools``, then you
1548would set ``RDEPENDS_${PN}-tools``, and so forth. 1548would set ``RDEPENDS:${PN}-tools``, and so forth.
1549 1549
1550Some runtime dependencies will be set automatically at packaging time. 1550Some runtime dependencies will be set automatically at packaging time.
1551These dependencies include any shared library dependencies (i.e. if a 1551These dependencies include any shared library dependencies (i.e. if a
@@ -1796,7 +1796,7 @@ the software being built:
1796 sure the install portion of the build completes with no issues. 1796 sure the install portion of the build completes with no issues.
1797 However, if you wish to install additional files not already being 1797 However, if you wish to install additional files not already being
1798 installed by ``make install``, you should do this using a 1798 installed by ``make install``, you should do this using a
1799 ``do_install_append`` function using the install command as described 1799 ``do_install:append`` function using the install command as described
1800 in the "Manual" bulleted item later in this list. 1800 in the "Manual" bulleted item later in this list.
1801 1801
1802- *Other (using* ``make install``\ *)*: You need to define a ``do_install`` 1802- *Other (using* ``make install``\ *)*: You need to define a ``do_install``
@@ -1865,9 +1865,9 @@ additional definitions in your recipe.
1865 1865
1866If you are adding services and the service initialization script or the 1866If you are adding services and the service initialization script or the
1867service file itself is not installed, you must provide for that 1867service file itself is not installed, you must provide for that
1868installation in your recipe using a ``do_install_append`` function. If 1868installation in your recipe using a ``do_install:append`` function. If
1869your recipe already has a ``do_install`` function, update the function 1869your recipe already has a ``do_install`` function, update the function
1870near its end rather than adding an additional ``do_install_append`` 1870near its end rather than adding an additional ``do_install:append``
1871function. 1871function.
1872 1872
1873When you create the installation for your services, you need to 1873When you create the installation for your services, you need to
@@ -1938,7 +1938,7 @@ take. The following list describes the process:
1938 discover problems, you can set 1938 discover problems, you can set
1939 :term:`PACKAGES`, 1939 :term:`PACKAGES`,
1940 :term:`FILES`, 1940 :term:`FILES`,
1941 ``do_install(_append)``, and so forth as needed. 1941 ``do_install(:append)``, and so forth as needed.
1942 1942
1943- *Splitting an Application into Multiple Packages*: If you need to 1943- *Splitting an Application into Multiple Packages*: If you need to
1944 split an application into several packages, see the 1944 split an application into several packages, see the
@@ -2137,7 +2137,7 @@ Post-Installation Scripts
2137Post-installation scripts run immediately after installing a package on 2137Post-installation scripts run immediately after installing a package on
2138the target or during image creation when a package is included in an 2138the target or during image creation when a package is included in an
2139image. To add a post-installation script to a package, add a 2139image. To add a post-installation script to a package, add a
2140``pkg_postinst_``\ `PACKAGENAME`\ ``()`` function to the recipe file 2140``pkg_postinst:``\ `PACKAGENAME`\ ``()`` function to the recipe file
2141(``.bb``) and replace `PACKAGENAME` with the name of the package you want 2141(``.bb``) and replace `PACKAGENAME` with the name of the package you want
2142to attach to the ``postinst`` script. To apply the post-installation 2142to attach to the ``postinst`` script. To apply the post-installation
2143script to the main package for the recipe, which is usually what is 2143script to the main package for the recipe, which is usually what is
@@ -2147,7 +2147,7 @@ PACKAGENAME.
2147 2147
2148A post-installation function has the following structure:: 2148A post-installation function has the following structure::
2149 2149
2150 pkg_postinst_PACKAGENAME() { 2150 pkg_postinst:PACKAGENAME() {
2151 # Commands to carry out 2151 # Commands to carry out
2152 } 2152 }
2153 2153
@@ -2367,7 +2367,7 @@ In the previous example, we want to ship the ``sxpm`` and ``cxpm``
2367binaries in separate packages. Since ``bindir`` would be packaged into 2367binaries in separate packages. Since ``bindir`` would be packaged into
2368the main :term:`PN` package by default, we prepend the :term:`PACKAGES` variable 2368the main :term:`PN` package by default, we prepend the :term:`PACKAGES` variable
2369so additional package names are added to the start of list. This results 2369so additional package names are added to the start of list. This results
2370in the extra ``FILES_*`` variables then containing information that 2370in the extra ``FILES:*`` variables then containing information that
2371define which files and directories go into which packages. Files 2371define which files and directories go into which packages. Files
2372included by earlier packages are skipped by latter packages. Thus, the 2372included by earlier packages are skipped by latter packages. Thus, the
2373main :term:`PN` package does not include the above listed files. 2373main :term:`PN` package does not include the above listed files.
@@ -2398,7 +2398,7 @@ configure and compile steps as well as sets things up to grab packages
2398from the appropriate area. In particular, this class sets ``noexec`` on 2398from the appropriate area. In particular, this class sets ``noexec`` on
2399both the :ref:`ref-tasks-configure` 2399both the :ref:`ref-tasks-configure`
2400and :ref:`ref-tasks-compile` tasks, 2400and :ref:`ref-tasks-compile` tasks,
2401sets ``FILES_${PN}`` to "/" so that it picks up all files, and sets up a 2401sets ``FILES:${PN}`` to "/" so that it picks up all files, and sets up a
2402:ref:`ref-tasks-install` task, which 2402:ref:`ref-tasks-install` task, which
2403effectively copies all files from ``${S}`` to ``${D}``. The 2403effectively copies all files from ``${S}`` to ``${D}``. The
2404``bin_package`` class works well when the files extracted into ``${S}`` 2404``bin_package`` class works well when the files extracted into ``${S}``
@@ -2459,7 +2459,7 @@ doing the following:
2459 2459
2460- Ensure that you set up :term:`FILES` 2460- Ensure that you set up :term:`FILES`
2461 (usually 2461 (usually
2462 ``FILES_${``\ :term:`PN`\ ``}``) to 2462 ``FILES:${``\ :term:`PN`\ ``}``) to
2463 point to the files you have installed, which of course depends on 2463 point to the files you have installed, which of course depends on
2464 where you have installed them and whether those files are in 2464 where you have installed them and whether those files are in
2465 different locations than the defaults. 2465 different locations than the defaults.
@@ -2631,7 +2631,7 @@ in the BitBake User Manual.
2631 2631
2632 VAR =+ "Starts" 2632 VAR =+ "Starts"
2633 2633
2634- *Appending (_append):* Use the ``_append`` operator to append values 2634- *Appending (:append):* Use the ``:append`` operator to append values
2635 to existing variables. This operator does not add any additional 2635 to existing variables. This operator does not add any additional
2636 space. Also, the operator is applied after all the ``+=``, and ``=+`` 2636 space. Also, the operator is applied after all the ``+=``, and ``=+``
2637 operators have been applied and after all ``=`` assignments have 2637 operators have been applied and after all ``=`` assignments have
@@ -2644,12 +2644,12 @@ in the BitBake User Manual.
2644 SRC_URI:append = " file://fix-makefile.patch" 2644 SRC_URI:append = " file://fix-makefile.patch"
2645 2645
2646 You can also use 2646 You can also use
2647 the ``_append`` operator with overrides, which results in the actions 2647 the ``:append`` operator with overrides, which results in the actions
2648 only being performed for the specified target or machine:: 2648 only being performed for the specified target or machine::
2649 2649
2650 SRC_URI:append:sh4 = " file://fix-makefile.patch" 2650 SRC_URI:append:sh4 = " file://fix-makefile.patch"
2651 2651
2652- *Prepending (_prepend):* Use the ``_prepend`` operator to prepend 2652- *Prepending (:prepend):* Use the ``:prepend`` operator to prepend
2653 values to existing variables. This operator does not add any 2653 values to existing variables. This operator does not add any
2654 additional space. Also, the operator is applied after all the ``+=``, 2654 additional space. Also, the operator is applied after all the ``+=``,
2655 and ``=+`` operators have been applied and after all ``=`` 2655 and ``=+`` operators have been applied and after all ``=``
@@ -2662,7 +2662,7 @@ in the BitBake User Manual.
2662 CFLAGS:prepend = "-I${S}/myincludes " 2662 CFLAGS:prepend = "-I${S}/myincludes "
2663 2663
2664 You can also use the 2664 You can also use the
2665 ``_prepend`` operator with overrides, which results in the actions 2665 ``:prepend`` operator with overrides, which results in the actions
2666 only being performed for the specified target or machine:: 2666 only being performed for the specified target or machine::
2667 2667
2668 CFLAGS:prepend:sh4 = "-I${S}/myincludes " 2668 CFLAGS:prepend:sh4 = "-I${S}/myincludes "
@@ -4538,7 +4538,7 @@ that can help you speed up the build:
4538 exceptions:: 4538 exceptions::
4539 4539
4540 STATICLIBCONF = "--disable-static" 4540 STATICLIBCONF = "--disable-static"
4541 STATICLIBCONF_sqlite3-native = "" 4541 STATICLIBCONF:sqlite3-native = ""
4542 EXTRA_OECONF += "${STATICLIBCONF}" 4542 EXTRA_OECONF += "${STATICLIBCONF}"
4543 4543
4544 .. note:: 4544 .. note::
@@ -4578,7 +4578,7 @@ can control which static library files (``*.a`` files) get included in
4578the built library. 4578the built library.
4579 4579
4580The :term:`PACKAGES` and 4580The :term:`PACKAGES` and
4581:term:`FILES_* <FILES>` variables in the 4581:term:`FILES:* <FILES>` variables in the
4582``meta/conf/bitbake.conf`` configuration file define how files installed 4582``meta/conf/bitbake.conf`` configuration file define how files installed
4583by the ``do_install`` task are packaged. By default, the :term:`PACKAGES` 4583by the ``do_install`` task are packaged. By default, the :term:`PACKAGES`
4584variable includes ``${PN}-staticdev``, which represents all static 4584variable includes ``${PN}-staticdev``, which represents all static
@@ -6510,8 +6510,8 @@ function in your recipe. The ``do_split_packages`` function searches for
6510a pattern of files or directories under a specified path and creates a 6510a pattern of files or directories under a specified path and creates a
6511package for each one it finds by appending to the 6511package for each one it finds by appending to the
6512:term:`PACKAGES` variable and 6512:term:`PACKAGES` variable and
6513setting the appropriate values for ``FILES_packagename``, 6513setting the appropriate values for ``FILES:packagename``,
6514``RDEPENDS_packagename``, ``DESCRIPTION_packagename``, and so forth. 6514``RDEPENDS:packagename``, ``DESCRIPTION:packagename``, and so forth.
6515Here is an example from the ``lighttpd`` recipe:: 6515Here is an example from the ``lighttpd`` recipe::
6516 6516
6517 python populate_packages:prepend () { 6517 python populate_packages:prepend () {
@@ -7389,11 +7389,11 @@ The variable can be used in multiple ways, including using suffixes to
7389set it for a specific package type and/or package. Note that the order 7389set it for a specific package type and/or package. Note that the order
7390of precedence is the same as this list: 7390of precedence is the same as this list:
7391 7391
7392- ``PACKAGE_ADD_METADATA_<PKGTYPE>_<PN>`` 7392- ``PACKAGE_ADD_METADATA_<PKGTYPE>:<PN>``
7393 7393
7394- ``PACKAGE_ADD_METADATA_<PKGTYPE>`` 7394- ``PACKAGE_ADD_METADATA_<PKGTYPE>``
7395 7395
7396- ``PACKAGE_ADD_METADATA_<PN>`` 7396- ``PACKAGE_ADD_METADATA:<PN>``
7397 7397
7398- :term:`PACKAGE_ADD_METADATA` 7398- :term:`PACKAGE_ADD_METADATA`
7399 7399
@@ -7664,11 +7664,11 @@ configuration file contains the line::
7664This line pulls in the 7664This line pulls in the
7665listed include file that contains numerous lines of exactly that form:: 7665listed include file that contains numerous lines of exactly that form::
7666 7666
7667 #SRCREV_pn-opkg-native ?= "${AUTOREV}" 7667 #SRCREV:pn-opkg-native ?= "${AUTOREV}"
7668 #SRCREV_pn-opkg-sdk ?= "${AUTOREV}" 7668 #SRCREV:pn-opkg-sdk ?= "${AUTOREV}"
7669 #SRCREV_pn-opkg ?= "${AUTOREV}" 7669 #SRCREV:pn-opkg ?= "${AUTOREV}"
7670 #SRCREV_pn-opkg-utils-native ?= "${AUTOREV}" 7670 #SRCREV:pn-opkg-utils-native ?= "${AUTOREV}"
7671 #SRCREV_pn-opkg-utils ?= "${AUTOREV}" 7671 #SRCREV:pn-opkg-utils ?= "${AUTOREV}"
7672 SRCREV:pn-gconf-dbus ?= "${AUTOREV}" 7672 SRCREV:pn-gconf-dbus ?= "${AUTOREV}"
7673 SRCREV:pn-matchbox-common ?= "${AUTOREV}" 7673 SRCREV:pn-matchbox-common ?= "${AUTOREV}"
7674 SRCREV:pn-matchbox-config-gtk ?= "${AUTOREV}" 7674 SRCREV:pn-matchbox-config-gtk ?= "${AUTOREV}"
@@ -8941,7 +8941,7 @@ In addition to variable values, the output of the ``bitbake -e`` and
8941- After the variable values, all functions appear in the output. For 8941- After the variable values, all functions appear in the output. For
8942 shell functions, variables referenced within the function body are 8942 shell functions, variables referenced within the function body are
8943 expanded. If a function has been modified using overrides or using 8943 expanded. If a function has been modified using overrides or using
8944 override-style operators like ``_append`` and ``_prepend``, then the 8944 override-style operators like ``:append`` and ``:prepend``, then the
8945 final assembled function body appears in the output. 8945 final assembled function body appears in the output.
8946 8946
8947Viewing Package Information with ``oe-pkgdata-util`` 8947Viewing Package Information with ``oe-pkgdata-util``
diff --git a/documentation/kernel-dev/advanced.rst b/documentation/kernel-dev/advanced.rst
index 9c3a478cb9..2dbcca60c1 100644
--- a/documentation/kernel-dev/advanced.rst
+++ b/documentation/kernel-dev/advanced.rst
@@ -724,7 +724,7 @@ If the BSP description is in recipe space, you cannot simply list the
724``*.scc`` in the :term:`SRC_URI` statement. You need to use the following 724``*.scc`` in the :term:`SRC_URI` statement. You need to use the following
725form from your kernel append file:: 725form from your kernel append file::
726 726
727 SRC_URI:append_myplatform = " \ 727 SRC_URI:append:myplatform = " \
728 file://myplatform;type=kmeta;destsuffix=myplatform \ 728 file://myplatform;type=kmeta;destsuffix=myplatform \
729 " 729 "
730 730
diff --git a/documentation/kernel-dev/common.rst b/documentation/kernel-dev/common.rst
index 331e982aca..7bfa468dec 100644
--- a/documentation/kernel-dev/common.rst
+++ b/documentation/kernel-dev/common.rst
@@ -502,23 +502,23 @@ strings in the file from the ``meta-yocto-bsp`` layer upstream.
502 KMACHINE:genericx86 ?= "common-pc" 502 KMACHINE:genericx86 ?= "common-pc"
503 KMACHINE:genericx86-64 ?= "common-pc-64" 503 KMACHINE:genericx86-64 ?= "common-pc-64"
504 KBRANCH:edgerouter = "standard/edgerouter" 504 KBRANCH:edgerouter = "standard/edgerouter"
505 KBRANCH_beaglebone = "standard/beaglebone" 505 KBRANCH:beaglebone = "standard/beaglebone"
506 506
507 SRCREV_machine:genericx86 ?= "d09f2ce584d60ecb7890550c22a80c48b83c2e19" 507 SRCREV_machine:genericx86 ?= "d09f2ce584d60ecb7890550c22a80c48b83c2e19"
508 SRCREV_machine:genericx86-64 ?= "d09f2ce584d60ecb7890550c22a80c48b83c2e19" 508 SRCREV_machine:genericx86-64 ?= "d09f2ce584d60ecb7890550c22a80c48b83c2e19"
509 SRCREV_machine:edgerouter ?= "b5c8cfda2dfe296410d51e131289fb09c69e1e7d" 509 SRCREV_machine:edgerouter ?= "b5c8cfda2dfe296410d51e131289fb09c69e1e7d"
510 SRCREV_machine_beaglebone ?= "b5c8cfda2dfe296410d51e131289fb09c69e1e7d" 510 SRCREV_machine:beaglebone ?= "b5c8cfda2dfe296410d51e131289fb09c69e1e7d"
511 511
512 512
513 COMPATIBLE_MACHINE:genericx86 = "genericx86" 513 COMPATIBLE_MACHINE:genericx86 = "genericx86"
514 COMPATIBLE_MACHINE:genericx86-64 = "genericx86-64" 514 COMPATIBLE_MACHINE:genericx86-64 = "genericx86-64"
515 COMPATIBLE_MACHINE:edgerouter = "edgerouter" 515 COMPATIBLE_MACHINE:edgerouter = "edgerouter"
516 COMPATIBLE_MACHINE_beaglebone = "beaglebone" 516 COMPATIBLE_MACHINE:beaglebone = "beaglebone"
517 517
518 LINUX_VERSION:genericx86 = "4.12.7" 518 LINUX_VERSION:genericx86 = "4.12.7"
519 LINUX_VERSION:genericx86-64 = "4.12.7" 519 LINUX_VERSION:genericx86-64 = "4.12.7"
520 LINUX_VERSION:edgerouter = "4.12.10" 520 LINUX_VERSION:edgerouter = "4.12.10"
521 LINUX_VERSION_beaglebone = "4.12.10" 521 LINUX_VERSION:beaglebone = "4.12.10"
522 522
523This append file 523This append file
524contains statements used to support several BSPs that ship with the 524contains statements used to support several BSPs that ship with the
@@ -726,7 +726,7 @@ that assigns the :term:`KBUILD_DEFCONFIG` variable based on "raspberrypi2"
726and provides the path to the "in-tree" ``defconfig`` file to be used for 726and provides the path to the "in-tree" ``defconfig`` file to be used for
727a Raspberry Pi 2, which is based on the Broadcom 2708/2709 chipset:: 727a Raspberry Pi 2, which is based on the Broadcom 2708/2709 chipset::
728 728
729 KBUILD_DEFCONFIG_raspberrypi2 ?= "bcm2709_defconfig" 729 KBUILD_DEFCONFIG:raspberrypi2 ?= "bcm2709_defconfig"
730 730
731Aside from modifying your kernel recipe and providing your own 731Aside from modifying your kernel recipe and providing your own
732``defconfig`` file, you need to be sure no files or statements set 732``defconfig`` file, you need to be sure no files or statements set
diff --git a/documentation/kernel-dev/faq.rst b/documentation/kernel-dev/faq.rst
index f0a7af37bb..47be334860 100644
--- a/documentation/kernel-dev/faq.rst
+++ b/documentation/kernel-dev/faq.rst
@@ -36,7 +36,7 @@ How do I install/not-install the kernel image on the rootfs?
36The kernel image (e.g. ``vmlinuz``) is provided by the 36The kernel image (e.g. ``vmlinuz``) is provided by the
37``kernel-image`` package. Image recipes depend on ``kernel-base``. To 37``kernel-image`` package. Image recipes depend on ``kernel-base``. To
38specify whether or not the kernel image is installed in the generated 38specify whether or not the kernel image is installed in the generated
39root filesystem, override ``RDEPENDS_${KERNEL_PACKAGE_NAME}-base`` to include or not 39root filesystem, override ``RDEPENDS:${KERNEL_PACKAGE_NAME}-base`` to include or not
40include "kernel-image". See the 40include "kernel-image". See the
41":ref:`dev-manual/common-tasks:using .bbappend files in your layer`" 41":ref:`dev-manual/common-tasks:using .bbappend files in your layer`"
42section in the 42section in the
diff --git a/documentation/overview-manual/concepts.rst b/documentation/overview-manual/concepts.rst
index 4f8e6cb041..b06a73e5fc 100644
--- a/documentation/overview-manual/concepts.rst
+++ b/documentation/overview-manual/concepts.rst
@@ -1768,7 +1768,7 @@ It is also worth noting that the end result of these signature
1768generators is to make some dependency and hash information available to 1768generators is to make some dependency and hash information available to
1769the build. This information includes: 1769the build. This information includes:
1770 1770
1771- ``BB_BASEHASH_task-``\ taskname: The base hashes for each task in the 1771- ``BB_BASEHASH:task-``\ taskname: The base hashes for each task in the
1772 recipe. 1772 recipe.
1773 1773
1774- ``BB_BASEHASH_``\ filename\ ``:``\ taskname: The base hashes for each 1774- ``BB_BASEHASH_``\ filename\ ``:``\ taskname: The base hashes for each
@@ -2027,7 +2027,7 @@ dependencies, you must manually declare the dependencies.
2027 .. note:: 2027 .. note::
2028 2028
2029 By default, ``foo-dev`` also has an :term:`RDEPENDS`-style dependency on 2029 By default, ``foo-dev`` also has an :term:`RDEPENDS`-style dependency on
2030 ``foo``, because the default value of ``RDEPENDS_${PN}-dev`` (set in 2030 ``foo``, because the default value of ``RDEPENDS:${PN}-dev`` (set in
2031 bitbake.conf) includes "${PN}". 2031 bitbake.conf) includes "${PN}".
2032 2032
2033 To ensure that the dependency chain is never broken, ``-dev`` and 2033 To ensure that the dependency chain is never broken, ``-dev`` and
diff --git a/documentation/overview-manual/yp-intro.rst b/documentation/overview-manual/yp-intro.rst
index d20a4ab09f..7aee9db04f 100644
--- a/documentation/overview-manual/yp-intro.rst
+++ b/documentation/overview-manual/yp-intro.rst
@@ -738,7 +738,7 @@ other build process, in which case the basic functionality can be
738defined by the classes it inherits from the OE-Core layer's class 738defined by the classes it inherits from the OE-Core layer's class
739definitions in ``./meta/classes``. Within a recipe you can also define 739definitions in ``./meta/classes``. Within a recipe you can also define
740additional tasks as well as task prerequisites. Recipe syntax through 740additional tasks as well as task prerequisites. Recipe syntax through
741BitBake also supports both ``_prepend`` and ``_append`` operators as a 741BitBake also supports both ``:prepend`` and ``:append`` operators as a
742method of extending task functionality. These operators inject code into 742method of extending task functionality. These operators inject code into
743the beginning or end of a task. For information on these BitBake 743the beginning or end of a task. For information on these BitBake
744operators, see the 744operators, see the
diff --git a/documentation/ref-manual/classes.rst b/documentation/ref-manual/classes.rst
index 610d64bd46..3af023895e 100644
--- a/documentation/ref-manual/classes.rst
+++ b/documentation/ref-manual/classes.rst
@@ -1198,7 +1198,7 @@ Here are the tests you can list with the :term:`WARN_QA` and
1198 its :term:`PN` value matches something already in :term:`OVERRIDES` (e.g. 1198 its :term:`PN` value matches something already in :term:`OVERRIDES` (e.g.
1199 :term:`PN` happens to be the same as :term:`MACHINE` or 1199 :term:`PN` happens to be the same as :term:`MACHINE` or
1200 :term:`DISTRO`), it can have unexpected consequences. 1200 :term:`DISTRO`), it can have unexpected consequences.
1201 For example, assignments such as ``FILES_${PN} = "xyz"`` effectively 1201 For example, assignments such as ``FILES:${PN} = "xyz"`` effectively
1202 turn into ``FILES = "xyz"``. 1202 turn into ``FILES = "xyz"``.
1203 1203
1204- ``rpaths:`` Checks for rpaths in the binaries that contain build 1204- ``rpaths:`` Checks for rpaths in the binaries that contain build
@@ -1224,7 +1224,7 @@ Here are the tests you can list with the :term:`WARN_QA` and
1224 1224
1225- ``unlisted-pkg-lics:`` Checks that all declared licenses applying 1225- ``unlisted-pkg-lics:`` Checks that all declared licenses applying
1226 for a package are also declared on the recipe level (i.e. any license 1226 for a package are also declared on the recipe level (i.e. any license
1227 in ``LICENSE_*`` should appear in :term:`LICENSE`). 1227 in ``LICENSE:*`` should appear in :term:`LICENSE`).
1228 1228
1229- ``useless-rpaths:`` Checks for dynamic library load paths (rpaths) 1229- ``useless-rpaths:`` Checks for dynamic library load paths (rpaths)
1230 in the binaries that by default on a standard system are searched by 1230 in the binaries that by default on a standard system are searched by
@@ -1621,7 +1621,7 @@ a couple different ways:
1621 BBCLASSEXTEND = "native" 1621 BBCLASSEXTEND = "native"
1622 1622
1623 Inside the 1623 Inside the
1624 recipe, use ``_class-native`` and ``_class-target`` overrides to 1624 recipe, use ``:class-native`` and ``:class-target`` overrides to
1625 specify any functionality specific to the respective native or target 1625 specify any functionality specific to the respective native or target
1626 case. 1626 case.
1627 1627
@@ -1652,7 +1652,7 @@ couple different ways:
1652 BBCLASSEXTEND = "nativesdk" 1652 BBCLASSEXTEND = "nativesdk"
1653 1653
1654 Inside the 1654 Inside the
1655 recipe, use ``_class-nativesdk`` and ``_class-target`` overrides to 1655 recipe, use ``:class-nativesdk`` and ``:class-target`` overrides to
1656 specify any functionality specific to the respective SDK machine or 1656 specify any functionality specific to the respective SDK machine or
1657 target case. 1657 target case.
1658 1658
diff --git a/documentation/ref-manual/qa-checks.rst b/documentation/ref-manual/qa-checks.rst
index 4b5d0abdba..d452de4119 100644
--- a/documentation/ref-manual/qa-checks.rst
+++ b/documentation/ref-manual/qa-checks.rst
@@ -263,7 +263,7 @@ Errors and Warnings
263 263
264 The ``/usr/share/info/dir`` should not be packaged. Add the following 264 The ``/usr/share/info/dir`` should not be packaged. Add the following
265 line to your :ref:`ref-tasks-install` task or to your 265 line to your :ref:`ref-tasks-install` task or to your
266 ``do_install_append`` within the recipe as follows:: 266 ``do_install:append`` within the recipe as follows::
267 267
268 rm ${D}${infodir}/dir 268 rm ${D}${infodir}/dir
269   269  
@@ -347,7 +347,7 @@ Errors and Warnings
347   347  
348.. _qa-check-dep-cmp: 348.. _qa-check-dep-cmp:
349 349
350- ``<var>_<packagename> is invalid: <comparison> (<value>) only comparisons <, =, >, <=, and >= are allowed [dep-cmp]`` 350- ``<var>:<packagename> is invalid: <comparison> (<value>) only comparisons <, =, >, <=, and >= are allowed [dep-cmp]``
351 351
352 If you are adding a versioned dependency relationship to one of the 352 If you are adding a versioned dependency relationship to one of the
353 dependency variables (:term:`RDEPENDS`, 353 dependency variables (:term:`RDEPENDS`,
@@ -454,14 +454,14 @@ Errors and Warnings
454 ``pkg_preinst``, ``pkg_postinst``, ``pkg_prerm``, ``pkg_postrm``, and 454 ``pkg_preinst``, ``pkg_postinst``, ``pkg_prerm``, ``pkg_postrm``, and
455 :term:`ALLOW_EMPTY`) should always be set specific 455 :term:`ALLOW_EMPTY`) should always be set specific
456 to a package (i.e. they should be set with a package name override 456 to a package (i.e. they should be set with a package name override
457 such as ``RDEPENDS_${PN} = "value"`` rather than 457 such as ``RDEPENDS:${PN} = "value"`` rather than
458 ``RDEPENDS = "value"``). If you receive this error, correct any 458 ``RDEPENDS = "value"``). If you receive this error, correct any
459 assignments to these variables within your recipe. 459 assignments to these variables within your recipe.
460 460
461 461
462- ``recipe uses DEPENDS_${PN}, should use DEPENDS [pkgvarcheck]`` 462- ``recipe uses DEPENDS:${PN}, should use DEPENDS [pkgvarcheck]``
463 463
464 This check looks for instances of setting ``DEPENDS_${PN}`` 464 This check looks for instances of setting ``DEPENDS:${PN}``
465 which is erroneous (:term:`DEPENDS` is a recipe-wide variable and thus 465 which is erroneous (:term:`DEPENDS` is a recipe-wide variable and thus
466 it is not correct to specify it for a particular package, nor will such 466 it is not correct to specify it for a particular package, nor will such
467 an assignment actually work.) Set :term:`DEPENDS` instead. 467 an assignment actually work.) Set :term:`DEPENDS` instead.
@@ -524,7 +524,7 @@ Errors and Warnings
524 following: 524 following:
525 525
526 - Add the files to :term:`FILES` for the package you want them to appear 526 - Add the files to :term:`FILES` for the package you want them to appear
527 in (e.g. ``FILES_${``\ :term:`PN`\ ``}`` for the main 527 in (e.g. ``FILES:${``\ :term:`PN`\ ``}`` for the main
528 package). 528 package).
529 529
530 - Delete the files at the end of the ``do_install`` task if the 530 - Delete the files at the end of the ``do_install`` task if the
@@ -546,11 +546,11 @@ Errors and Warnings
546 546
547.. _qa-check-unlisted-pkg-lics: 547.. _qa-check-unlisted-pkg-lics:
548 548
549- ``LICENSE_<packagename> includes licenses (<licenses>) that are not listed in LICENSE [unlisted-pkg-lics]`` 549- ``LICENSE:<packagename> includes licenses (<licenses>) that are not listed in LICENSE [unlisted-pkg-lics]``
550 550
551 The :term:`LICENSE` of the recipe should be a superset 551 The :term:`LICENSE` of the recipe should be a superset
552 of all the licenses of all packages produced by this recipe. In other 552 of all the licenses of all packages produced by this recipe. In other
553 words, any license in ``LICENSE_*`` should also appear in 553 words, any license in ``LICENSE:*`` should also appear in
554 :term:`LICENSE`. 554 :term:`LICENSE`.
555 555
556 556
diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index c2b75dff84..d5df9ae41c 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -575,7 +575,7 @@ system and gives an overview of their function and contents.
575 575
576 Internally, the :term:`BBCLASSEXTEND` mechanism generates recipe 576 Internally, the :term:`BBCLASSEXTEND` mechanism generates recipe
577 variants by rewriting variable values and applying overrides such 577 variants by rewriting variable values and applying overrides such
578 as ``_class-native``. For example, to generate a native version of 578 as ``:class-native``. For example, to generate a native version of
579 a recipe, a :term:`DEPENDS` on "foo" is rewritten 579 a recipe, a :term:`DEPENDS` on "foo" is rewritten
580 to a :term:`DEPENDS` on "foo-native". 580 to a :term:`DEPENDS` on "foo-native".
581 581
@@ -2358,7 +2358,7 @@ system and gives an overview of their function and contents.
2358 rather than ``/usr/bin``. You can find a list of these 2358 rather than ``/usr/bin``. You can find a list of these
2359 variables at the top of the ``meta/conf/bitbake.conf`` file in 2359 variables at the top of the ``meta/conf/bitbake.conf`` file in
2360 the :term:`Source Directory`. You will also 2360 the :term:`Source Directory`. You will also
2361 find the default values of the various ``FILES_*`` variables in 2361 find the default values of the various ``FILES:*`` variables in
2362 this file. 2362 this file.
2363 2363
2364 If some of the files you provide with the :term:`FILES` variable are 2364 If some of the files you provide with the :term:`FILES` variable are
@@ -2427,7 +2427,7 @@ system and gives an overview of their function and contents.
2427 a :term:`MACHINE`-specific override, which is useful 2427 a :term:`MACHINE`-specific override, which is useful
2428 in a BSP layer:: 2428 in a BSP layer::
2429 2429
2430 FILESEXTRAPATHS:prepend_intel-x86-common := "${THISDIR}/${PN}:" 2430 FILESEXTRAPATHS:prepend:intel-x86-common := "${THISDIR}/${PN}:"
2431 2431
2432 The previous statement appears in the 2432 The previous statement appears in the
2433 ``linux-yocto-dev.bbappend`` file, which is found in the 2433 ``linux-yocto-dev.bbappend`` file, which is found in the
@@ -3044,8 +3044,8 @@ system and gives an overview of their function and contents.
3044 :term:`IMAGE_FSTYPES` prior to using the "inherit image" line. 3044 :term:`IMAGE_FSTYPES` prior to using the "inherit image" line.
3045 3045
3046 - Due to the way the OpenEmbedded build system processes this 3046 - Due to the way the OpenEmbedded build system processes this
3047 variable, you cannot update its contents by using ``_append`` 3047 variable, you cannot update its contents by using ``:append``
3048 or ``_prepend``. You must use the ``+=`` operator to add one or 3048 or ``:prepend``. You must use the ``+=`` operator to add one or
3049 more options to the :term:`IMAGE_FSTYPES` variable. 3049 more options to the :term:`IMAGE_FSTYPES` variable.
3050 3050
3051 :term:`IMAGE_INSTALL` 3051 :term:`IMAGE_INSTALL`
@@ -3303,7 +3303,7 @@ system and gives an overview of their function and contents.
3303 Specifies a dependency from one image type on another. Here is an 3303 Specifies a dependency from one image type on another. Here is an
3304 example from the :ref:`image-live <ref-classes-image-live>` class:: 3304 example from the :ref:`image-live <ref-classes-image-live>` class::
3305 3305
3306 IMAGE_TYPEDEP_live = "ext3" 3306 IMAGE_TYPEDEP:live = "ext3"
3307 3307
3308 In the previous example, the variable ensures that when "live" is 3308 In the previous example, the variable ensures that when "live" is
3309 listed with the :term:`IMAGE_FSTYPES` variable, 3309 listed with the :term:`IMAGE_FSTYPES` variable,
@@ -3763,7 +3763,7 @@ system and gives an overview of their function and contents.
3763 KBRANCH:genericx86 = "standard/base" 3763 KBRANCH:genericx86 = "standard/base"
3764 KBRANCH:genericx86-64 = "standard/base" 3764 KBRANCH:genericx86-64 = "standard/base"
3765 KBRANCH:edgerouter = "standard/edgerouter" 3765 KBRANCH:edgerouter = "standard/edgerouter"
3766 KBRANCH_beaglebone = "standard/beaglebone" 3766 KBRANCH:beaglebone = "standard/beaglebone"
3767 3767
3768 The :term:`KBRANCH` statements 3768 The :term:`KBRANCH` statements
3769 identify the kernel branch to use when building for each supported 3769 identify the kernel branch to use when building for each supported
@@ -3791,11 +3791,11 @@ system and gives an overview of their function and contents.
3791 Here is an example from a "raspberrypi2" :term:`KMACHINE` build that uses 3791 Here is an example from a "raspberrypi2" :term:`KMACHINE` build that uses
3792 a ``defconfig`` file named "bcm2709_defconfig":: 3792 a ``defconfig`` file named "bcm2709_defconfig"::
3793 3793
3794 KBUILD_DEFCONFIG_raspberrypi2 = "bcm2709_defconfig" 3794 KBUILD_DEFCONFIG:raspberrypi2 = "bcm2709_defconfig"
3795 3795
3796 As an alternative, you can use the following within your append file:: 3796 As an alternative, you can use the following within your append file::
3797 3797
3798 KBUILD_DEFCONFIG:pn-linux-yocto ?= defconfig_file 3798 KBUILD_DEFCONFIG:pn-linux-yocto ?= "defconfig_file"
3799 3799
3800 For more 3800 For more
3801 information on how to use the :term:`KBUILD_DEFCONFIG` variable, see the 3801 information on how to use the :term:`KBUILD_DEFCONFIG` variable, see the
@@ -4128,13 +4128,13 @@ system and gives an overview of their function and contents.
4128 Kernel's ``meta`` branch. As an example take a look in the 4128 Kernel's ``meta`` branch. As an example take a look in the
4129 ``common/recipes-kernel/linux/linux-yocto_3.19.bbappend`` file:: 4129 ``common/recipes-kernel/linux/linux-yocto_3.19.bbappend`` file::
4130 4130
4131 LINUX_VERSION_core2-32-intel-common = "3.19.0" 4131 LINUX_VERSION:core2-32-intel-common = "3.19.0"
4132 COMPATIBLE_MACHINE_core2-32-intel-common = "${MACHINE}" 4132 COMPATIBLE_MACHINE:core2-32-intel-common = "${MACHINE}"
4133 SRCREV_meta_core2-32-intel-common = "8897ef68b30e7426bc1d39895e71fb155d694974" 4133 SRCREV_meta:core2-32-intel-common = "8897ef68b30e7426bc1d39895e71fb155d694974"
4134 SRCREV_machine_core2-32-intel-common = "43b9eced9ba8a57add36af07736344dcc383f711" 4134 SRCREV_machine:core2-32-intel-common = "43b9eced9ba8a57add36af07736344dcc383f711"
4135 KMACHINE_core2-32-intel-common = "intel-core2-32" 4135 KMACHINE:core2-32-intel-common = "intel-core2-32"
4136 KBRANCH_core2-32-intel-common = "standard/base" 4136 KBRANCH:core2-32-intel-common = "standard/base"
4137 KERNEL_FEATURES:append_core2-32-intel-common = "${KERNEL_FEATURES_INTEL_COMMON}" 4137 KERNEL_FEATURES:append:core2-32-intel-common = "${KERNEL_FEATURES_INTEL_COMMON}"
4138 4138
4139 The :term:`KMACHINE` statement says 4139 The :term:`KMACHINE` statement says
4140 that the kernel understands the machine name as "intel-core2-32". 4140 that the kernel understands the machine name as "intel-core2-32".
@@ -4322,7 +4322,7 @@ system and gives an overview of their function and contents.
4322 build system to create an extra package (i.e. 4322 build system to create an extra package (i.e.
4323 ``${``\ :term:`PN`\ ``}-lic``) for each recipe and to add 4323 ``${``\ :term:`PN`\ ``}-lic``) for each recipe and to add
4324 those packages to the 4324 those packages to the
4325 :term:`RRECOMMENDS`\ ``_${PN}``. 4325 :term:`RRECOMMENDS`\ ``:${PN}``.
4326 4326
4327 The ``${PN}-lic`` package installs a directory in 4327 The ``${PN}-lic`` package installs a directory in
4328 ``/usr/share/licenses`` named ``${PN}``, which is the recipe's base 4328 ``/usr/share/licenses`` named ``${PN}``, which is the recipe's base
@@ -4852,7 +4852,7 @@ system and gives an overview of their function and contents.
4852 4852
4853 :term:`NOAUTOPACKAGEDEBUG` 4853 :term:`NOAUTOPACKAGEDEBUG`
4854 Disables auto package from splitting ``.debug`` files. If a recipe 4854 Disables auto package from splitting ``.debug`` files. If a recipe
4855 requires ``FILES_${PN}-dbg`` to be set manually, the 4855 requires ``FILES:${PN}-dbg`` to be set manually, the
4856 :term:`NOAUTOPACKAGEDEBUG` can be defined allowing you to define the 4856 :term:`NOAUTOPACKAGEDEBUG` can be defined allowing you to define the
4857 content of the debug package. For example:: 4857 content of the debug package. For example::
4858 4858
@@ -4955,7 +4955,7 @@ system and gives an overview of their function and contents.
4955 assignment will override ``FOO`` with the value "overridden" at the 4955 assignment will override ``FOO`` with the value "overridden" at the
4956 end of parsing:: 4956 end of parsing::
4957 4957
4958 FOO_an-override = "overridden" 4958 FOO:an-override = "overridden"
4959 4959
4960 See the 4960 See the
4961 ":ref:`bitbake:bitbake-user-manual/bitbake-user-manual-metadata:conditional syntax (overrides)`" 4961 ":ref:`bitbake:bitbake-user-manual/bitbake-user-manual-metadata:conditional syntax (overrides)`"
@@ -5401,7 +5401,7 @@ system and gives an overview of their function and contents.
5401 (leftmost) package. 5401 (leftmost) package.
5402 5402
5403 Packages in the variable's list that are empty (i.e. where none of 5403 Packages in the variable's list that are empty (i.e. where none of
5404 the patterns in ``FILES_``\ pkg match any files installed by the 5404 the patterns in ``FILES:``\ pkg match any files installed by the
5405 :ref:`ref-tasks-install` task) are not generated, 5405 :ref:`ref-tasks-install` task) are not generated,
5406 unless generation is forced through the 5406 unless generation is forced through the
5407 :term:`ALLOW_EMPTY` variable. 5407 :term:`ALLOW_EMPTY` variable.
@@ -5552,7 +5552,7 @@ system and gives an overview of their function and contents.
5552 5552
5553 For example, when the :ref:`debian <ref-classes-debian>` class 5553 For example, when the :ref:`debian <ref-classes-debian>` class
5554 renames the output package, it does so by setting 5554 renames the output package, it does so by setting
5555 ``PKG_packagename``. 5555 ``PKG:packagename``.
5556 5556
5557 :term:`PKG_CONFIG_PATH` 5557 :term:`PKG_CONFIG_PATH`
5558 The path to ``pkg-config`` files for the current build context. 5558 The path to ``pkg-config`` files for the current build context.
@@ -5796,7 +5796,7 @@ system and gives an overview of their function and contents.
5796 5796
5797 .. note:: 5797 .. note::
5798 5798
5799 The ``\_forcevariable`` override is not handled specially. This override 5799 The ``:forcevariable`` override is not handled specially. This override
5800 only works because the default value of :term:`OVERRIDES` includes "forcevariable". 5800 only works because the default value of :term:`OVERRIDES` includes "forcevariable".
5801 5801
5802 If a recipe with the specified version is not available, a warning 5802 If a recipe with the specified version is not available, a warning
@@ -6083,10 +6083,10 @@ system and gives an overview of their function and contents.
6083 6083
6084 .. note:: 6084 .. note::
6085 6085
6086 ``RDEPENDS_${PN}-dev`` includes ``${``\ :term:`PN`\ ``}`` 6086 ``RDEPENDS:${PN}-dev`` includes ``${``\ :term:`PN`\ ``}``
6087 by default. This default is set in the BitBake configuration file 6087 by default. This default is set in the BitBake configuration file
6088 (``meta/conf/bitbake.conf``). Be careful not to accidentally remove 6088 (``meta/conf/bitbake.conf``). Be careful not to accidentally remove
6089 ``${PN}`` when modifying ``RDEPENDS_${PN}-dev``. Use the "+=" operator 6089 ``${PN}`` when modifying ``RDEPENDS:${PN}-dev``. Use the "+=" operator
6090 rather than the "=" operator. 6090 rather than the "=" operator.
6091 6091
6092 The package names you use with :term:`RDEPENDS` must appear as they would 6092 The package names you use with :term:`RDEPENDS` must appear as they would
@@ -6873,7 +6873,7 @@ system and gives an overview of their function and contents.
6873 defined in the ``meta/conf/bitbake.conf`` configuration file. 6873 defined in the ``meta/conf/bitbake.conf`` configuration file.
6874 6874
6875 You will see this variable referenced in the default values of 6875 You will see this variable referenced in the default values of
6876 ``FILES_${PN}``. 6876 ``FILES:${PN}``.
6877 6877
6878 :term:`SOLIBSDEV` 6878 :term:`SOLIBSDEV`
6879 Defines the suffix for the development symbolic link (symlink) for 6879 Defines the suffix for the development symbolic link (symlink) for
@@ -6882,7 +6882,7 @@ system and gives an overview of their function and contents.
6882 ``meta/conf/bitbake.conf`` configuration file. 6882 ``meta/conf/bitbake.conf`` configuration file.
6883 6883
6884 You will see this variable referenced in the default values of 6884 You will see this variable referenced in the default values of
6885 ``FILES_${PN}-dev``. 6885 ``FILES:${PN}-dev``.
6886 6886
6887 :term:`SOURCE_MIRROR_FETCH` 6887 :term:`SOURCE_MIRROR_FETCH`
6888 When you are fetching files to create a mirror of sources (i.e. 6888 When you are fetching files to create a mirror of sources (i.e.
diff --git a/documentation/sdk-manual/appendix-customizing.rst b/documentation/sdk-manual/appendix-customizing.rst
index 44f4334c29..4eccc28e9b 100644
--- a/documentation/sdk-manual/appendix-customizing.rst
+++ b/documentation/sdk-manual/appendix-customizing.rst
@@ -73,7 +73,7 @@ adjustments:
73 SDK_INHERIT_BLACKLIST 73 SDK_INHERIT_BLACKLIST
74 is set using the "?=" operator. Consequently, you will need to 74 is set using the "?=" operator. Consequently, you will need to
75 either define the entire list by using the "=" operator, or you 75 either define the entire list by using the "=" operator, or you
76 will need to append a value using either "_append" or the "+=" 76 will need to append a value using either ":append" or the "+="
77 operator. You can learn more about these operators in the 77 operator. You can learn more about these operators in the
78 ":ref:`bitbake:bitbake-user-manual/bitbake-user-manual-metadata:basic syntax`" 78 ":ref:`bitbake:bitbake-user-manual/bitbake-user-manual-metadata:basic syntax`"
79 section of the BitBake User Manual. 79 section of the BitBake User Manual.
@@ -250,7 +250,7 @@ source, you need to do a number of things:
250 recipes that depend on lists of other recipes. 250 recipes that depend on lists of other recipes.
251 251
252 - Build the "world" target and set 252 - Build the "world" target and set
253 ``EXCLUDE_FROM_WORLD_pn-``\ recipename for the recipes you do not 253 ``EXCLUDE_FROM_WORLD:pn-``\ recipename for the recipes you do not
254 want built. See the 254 want built. See the
255 :term:`EXCLUDE_FROM_WORLD` 255 :term:`EXCLUDE_FROM_WORLD`
256 variable for additional information. 256 variable for additional information.
@@ -334,7 +334,7 @@ within it are available. Having these recipes available increases build
334time significantly and increases the size of the SDK installer by 30-80 334time significantly and increases the size of the SDK installer by 30-80
335Mbytes depending on how many recipes are included in your configuration. 335Mbytes depending on how many recipes are included in your configuration.
336 336
337You can use ``EXCLUDE_FROM_WORLD_pn-``\ recipename for recipes you want 337You can use ``EXCLUDE_FROM_WORLD:pn-``\ recipename for recipes you want
338to exclude. However, it is assumed that you would need to be building 338to exclude. However, it is assumed that you would need to be building
339the "world" target if you want to provide additional items to the SDK. 339the "world" target if you want to provide additional items to the SDK.
340Consequently, building for "world" should not represent undue overhead 340Consequently, building for "world" should not represent undue overhead
diff --git a/documentation/sdk-manual/extensible.rst b/documentation/sdk-manual/extensible.rst
index bdce0414e4..8ef44e39ac 100644
--- a/documentation/sdk-manual/extensible.rst
+++ b/documentation/sdk-manual/extensible.rst
@@ -1154,7 +1154,7 @@ subdirectory for each package. Apart from some advanced cases, the
1154splitting. The :term:`PACKAGES` variable lists all of the packages to be 1154splitting. The :term:`PACKAGES` variable lists all of the packages to be
1155produced, while the :term:`FILES` variable specifies which files to include 1155produced, while the :term:`FILES` variable specifies which files to include
1156in each package by using an override to specify the package. For 1156in each package by using an override to specify the package. For
1157example, ``FILES_${PN}`` specifies the files to go into the main package 1157example, ``FILES:${PN}`` specifies the files to go into the main package
1158(i.e. the main package has the same name as the recipe and 1158(i.e. the main package has the same name as the recipe and
1159``${``\ :term:`PN`\ ``}`` evaluates to the 1159``${``\ :term:`PN`\ ``}`` evaluates to the
1160recipe name). The order of the :term:`PACKAGES` value is significant. For 1160recipe name). The order of the :term:`PACKAGES` value is significant. For
diff --git a/documentation/test-manual/reproducible-builds.rst b/documentation/test-manual/reproducible-builds.rst
index c66c82f86a..68fdf547bd 100644
--- a/documentation/test-manual/reproducible-builds.rst
+++ b/documentation/test-manual/reproducible-builds.rst
@@ -70,7 +70,7 @@ things we do within the build system to ensure reproducibility include:
70 70
71.. note:: 71.. note::
72 72
73 Because of an open bug in GCC, using ``DISTRO_FEATURES_append = " lto"`` or 73 Because of an open bug in GCC, using ``DISTRO_FEATURES:append = " lto"`` or
74 adding ``-flto`` (Link Time Optimization) to ``CFLAGS`` makes the resulting 74 adding ``-flto`` (Link Time Optimization) to ``CFLAGS`` makes the resulting
75 binary non-reproducible, in that it depends on the full absolute build path 75 binary non-reproducible, in that it depends on the full absolute build path
76 to ``recipe-sysroot-native``, so installing the Yocto Project in a different 76 to ``recipe-sysroot-native``, so installing the Yocto Project in a different