summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--documentation/dev-manual/common-tasks.rst196
1 files changed, 98 insertions, 98 deletions
diff --git a/documentation/dev-manual/common-tasks.rst b/documentation/dev-manual/common-tasks.rst
index 37077d72d4..7dcb8769d8 100644
--- a/documentation/dev-manual/common-tasks.rst
+++ b/documentation/dev-manual/common-tasks.rst
@@ -212,27 +212,27 @@ following list:
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``,
220 wherein the kernel compile and link options are adjusted in the 220 wherein the kernel compile and link options are adjusted in the
221 case of a subset of the supported architectures:: 221 case of a subset of the supported architectures::
222 222
223 DEPENDS_append_aarch64 = " libgcc" 223 DEPENDS:append:aarch64 = " libgcc"
224 KERNEL_CC_append_aarch64 = " ${TOOLCHAIN_OPTIONS}" 224 KERNEL_CC:append:aarch64 = " ${TOOLCHAIN_OPTIONS}"
225 KERNEL_LD_append_aarch64 = " ${TOOLCHAIN_OPTIONS}" 225 KERNEL_LD:append:aarch64 = " ${TOOLCHAIN_OPTIONS}"
226 226
227 DEPENDS_append_nios2 = " libgcc" 227 DEPENDS:append:nios2 = " libgcc"
228 KERNEL_CC_append_nios2 = " ${TOOLCHAIN_OPTIONS}" 228 KERNEL_CC:append:nios2 = " ${TOOLCHAIN_OPTIONS}"
229 KERNEL_LD_append_nios2 = " ${TOOLCHAIN_OPTIONS}" 229 KERNEL_LD:append:nios2 = " ${TOOLCHAIN_OPTIONS}"
230 230
231 DEPENDS_append_arc = " libgcc" 231 DEPENDS:append:arc = " libgcc"
232 KERNEL_CC_append_arc = " ${TOOLCHAIN_OPTIONS}" 232 KERNEL_CC:append:arc = " ${TOOLCHAIN_OPTIONS}"
233 KERNEL_LD_append_arc = " ${TOOLCHAIN_OPTIONS}" 233 KERNEL_LD:append:arc = " ${TOOLCHAIN_OPTIONS}"
234 234
235 KERNEL_FEATURES_append_qemuall=" features/debug/printk.scc" 235 KERNEL_FEATURES:append:qemuall=" features/debug/printk.scc"
236 236
237 .. note:: 237 .. note::
238 238
@@ -247,7 +247,7 @@ following list:
247 at ``meta-one/recipes-core/base-files/base-files.bbappend`` could 247 at ``meta-one/recipes-core/base-files/base-files.bbappend`` could
248 extend :term:`FILESPATH` using :term:`FILESEXTRAPATHS` as follows:: 248 extend :term:`FILESPATH` using :term:`FILESEXTRAPATHS` as follows::
249 249
250 FILESEXTRAPATHS_prepend := "${THISDIR}/${BPN}:" 250 FILESEXTRAPATHS:prepend := "${THISDIR}/${BPN}:"
251 251
252 The build for machine "one" will pick up your machine-specific file as 252 The build for machine "one" will pick up your machine-specific file as
253 long as you have the file in 253 long as you have the file in
@@ -512,7 +512,7 @@ Following is the append file, which is named ``formfactor_0.0.bbappend``
512and is from the Raspberry Pi BSP Layer named ``meta-raspberrypi``. The 512and is from the Raspberry Pi BSP Layer named ``meta-raspberrypi``. The
513file is in the layer at ``recipes-bsp/formfactor``:: 513file is in the layer at ``recipes-bsp/formfactor``::
514 514
515 FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" 515 FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}:"
516 516
517By default, the build system uses the 517By default, the build system uses the
518:term:`FILESPATH` variable to 518:term:`FILESPATH` variable to
@@ -832,7 +832,7 @@ all images, which might not be what you require.
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
@@ -850,7 +850,7 @@ As 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
853 IMAGE_INSTALL_append_pn-core-image-minimal = " strace" 853 IMAGE_INSTALL:append:pn-core-image-minimal = " strace"
854 854
855This example adds ``strace`` to the ``core-image-minimal`` image only. 855This example adds ``strace`` to the ``core-image-minimal`` image only.
856 856
@@ -976,17 +976,17 @@ the full packagegroup name ``packagegroup-custom``::
976 ${PN}-tools \ 976 ${PN}-tools \
977 " 977 "
978 978
979 RDEPENDS_${PN}-apps = "\ 979 RDEPENDS:${PN}-apps = "\
980 dropbear \ 980 dropbear \
981 portmap \ 981 portmap \
982 psplash" 982 psplash"
983 983
984 RDEPENDS_${PN}-tools = "\ 984 RDEPENDS:${PN}-tools = "\
985 oprofile \ 985 oprofile \
986 oprofileui-server \ 986 oprofileui-server \
987 lttng-tools" 987 lttng-tools"
988 988
989 RRECOMMENDS_${PN}-tools = "\ 989 RRECOMMENDS:${PN}-tools = "\
990 kernel-module-oprofile" 990 kernel-module-oprofile"
991 991
992In the previous example, two package group packages are created with 992In the previous example, two package group packages are created with
@@ -1013,7 +1013,7 @@ configuration file. Use the following in an append file::
1013 1013
1014Use the following in a configuration file:: 1014Use the following in a configuration file::
1015 1015
1016 hostname_pn-base-files = "myhostname" 1016 hostname:pn-base-files = "myhostname"
1017 1017
1018Changing the default value of the variable "hostname" can be useful in 1018Changing the default value of the variable "hostname" can be useful in
1019certain situations. For example, suppose you need to do extensive 1019certain situations. For example, suppose you need to do extensive
@@ -1028,7 +1028,7 @@ Another point of interest is that if you unset the variable, the image
1028will have no default hostname in the filesystem. Here is an example that 1028will have no default hostname in the filesystem. Here is an example that
1029unsets the variable in a configuration file:: 1029unsets the variable in a configuration file::
1030 1030
1031 hostname_pn-base-files = "" 1031 hostname:pn-base-files = ""
1032 1032
1033Having no default hostname in the filesystem is suitable for 1033Having no default hostname in the filesystem is suitable for
1034environments that use dynamic hostnames such as virtual machines. 1034environments that use dynamic hostnames such as virtual machines.
@@ -2300,7 +2300,7 @@ compiler. For example, the application might need an additional header
2300path. You can accomplish this by adding to the :term:`CFLAGS` variable. The 2300path. You can accomplish this by adding to the :term:`CFLAGS` variable. The
2301following example shows this:: 2301following example shows this::
2302 2302
2303 CFLAGS_prepend = "-I ${S}/include " 2303 CFLAGS:prepend = "-I ${S}/include "
2304 2304
2305In the following example, ``mtd-utils`` is a makefile-based package:: 2305In the following example, ``mtd-utils`` is a makefile-based package::
2306 2306
@@ -2330,9 +2330,9 @@ In the following example, ``mtd-utils`` is a makefile-based package::
2330 2330
2331 PACKAGES =+ "mtd-utils-jffs2 mtd-utils-ubifs mtd-utils-misc" 2331 PACKAGES =+ "mtd-utils-jffs2 mtd-utils-ubifs mtd-utils-misc"
2332 2332
2333 FILES_mtd-utils-jffs2 = "${sbindir}/mkfs.jffs2 ${sbindir}/jffs2dump ${sbindir}/jffs2reader ${sbindir}/sumtool" 2333 FILES:mtd-utils-jffs2 = "${sbindir}/mkfs.jffs2 ${sbindir}/jffs2dump ${sbindir}/jffs2reader ${sbindir}/sumtool"
2334 FILES_mtd-utils-ubifs = "${sbindir}/mkfs.ubifs ${sbindir}/ubi*" 2334 FILES:mtd-utils-ubifs = "${sbindir}/mkfs.ubifs ${sbindir}/ubi*"
2335 FILES_mtd-utils-misc = "${sbindir}/nftl* ${sbindir}/ftl* ${sbindir}/rfd* ${sbindir}/doc* ${sbindir}/serve_image ${sbindir}/recv_image" 2335 FILES:mtd-utils-misc = "${sbindir}/nftl* ${sbindir}/ftl* ${sbindir}/rfd* ${sbindir}/doc* ${sbindir}/serve_image ${sbindir}/recv_image"
2336 2336
2337 PARALLEL_MAKE = "" 2337 PARALLEL_MAKE = ""
2338 2338
@@ -2360,8 +2360,8 @@ into separate packages::
2360 XORG_PN = "libXpm" 2360 XORG_PN = "libXpm"
2361 2361
2362 PACKAGES =+ "sxpm cxpm" 2362 PACKAGES =+ "sxpm cxpm"
2363 FILES_cxpm = "${bindir}/cxpm" 2363 FILES:cxpm = "${bindir}/cxpm"
2364 FILES_sxpm = "${bindir}/sxpm" 2364 FILES:sxpm = "${bindir}/sxpm"
2365 2365
2366In the previous example, we want to ship the ``sxpm`` and ``cxpm`` 2366In 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
@@ -2504,7 +2504,7 @@ chapter of the BitBake User Manual.
2504 2504
2505 S = "${WORKDIR}/postfix-${PV}" 2505 S = "${WORKDIR}/postfix-${PV}"
2506 CFLAGS += "-DNO_ASM" 2506 CFLAGS += "-DNO_ASM"
2507 SRC_URI_append = " file://fixup.patch" 2507 SRC_URI:append = " file://fixup.patch"
2508 2508
2509- *Functions:* Functions provide a series of actions to be performed. 2509- *Functions:* Functions provide a series of actions to be performed.
2510 You usually use functions to override the default implementation of a 2510 You usually use functions to override the default implementation of a
@@ -2641,13 +2641,13 @@ in the BitBake User Manual.
2641 start to ensure the appended value is not merged with the existing 2641 start to ensure the appended value is not merged with the existing
2642 value:: 2642 value::
2643 2643
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
@@ -2659,13 +2659,13 @@ in the BitBake User Manual.
2659 end to ensure the prepended value is not merged with the existing 2659 end to ensure the prepended value is not merged with the existing
2660 value:: 2660 value::
2661 2661
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 "
2669 2669
2670- *Overrides:* You can use overrides to set a value conditionally, 2670- *Overrides:* You can use overrides to set a value conditionally,
2671 typically based on how the recipe is being built. For example, to set 2671 typically based on how the recipe is being built. For example, to set
@@ -2676,7 +2676,7 @@ in the BitBake User Manual.
2676 you would do the following:: 2676 you would do the following::
2677 2677
2678 KBRANCH = "standard/base" 2678 KBRANCH = "standard/base"
2679 KBRANCH_qemuarm = "standard/arm-versatile-926ejs" 2679 KBRANCH:qemuarm = "standard/arm-versatile-926ejs"
2680 2680
2681 Overrides are also used to separate 2681 Overrides are also used to separate
2682 alternate values of a variable in other situations. For example, when 2682 alternate values of a variable in other situations. For example, when
@@ -2951,7 +2951,7 @@ The following steps describe how to set up the AUH utility:
2951 If your distro does not enable by default ptest, which Poky 2951 If your distro does not enable by default ptest, which Poky
2952 does, you need the following in your ``local.conf`` file:: 2952 does, you need the following in your ``local.conf`` file::
2953 2953
2954 DISTRO_FEATURES_append = " ptest" 2954 DISTRO_FEATURES:append = " ptest"
2955 2955
2956 2956
29576. *Optionally Start a vncserver:* If you are running in a server 29576. *Optionally Start a vncserver:* If you are running in a server
@@ -4301,7 +4301,7 @@ point to your external source code. Here are the statements to put in
4301your ``local.conf`` file:: 4301your ``local.conf`` file::
4302 4302
4303 INHERIT += "externalsrc" 4303 INHERIT += "externalsrc"
4304 EXTERNALSRC_pn-myrecipe = "path-to-your-source-tree" 4304 EXTERNALSRC:pn-myrecipe = "path-to-your-source-tree"
4305 4305
4306This next example shows how to accomplish the same thing by setting 4306This next example shows how to accomplish the same thing by setting
4307:term:`EXTERNALSRC` in the recipe itself or in the recipe's append file:: 4307:term:`EXTERNALSRC` in the recipe itself or in the recipe's append file::
@@ -4323,7 +4323,7 @@ some other nominated directory, you can set
4323:term:`EXTERNALSRC_BUILD` 4323:term:`EXTERNALSRC_BUILD`
4324to point to that directory:: 4324to point to that directory::
4325 4325
4326 EXTERNALSRC_BUILD_pn-myrecipe = "path-to-your-source-tree" 4326 EXTERNALSRC_BUILD:pn-myrecipe = "path-to-your-source-tree"
4327 4327
4328Replicating a Build Offline 4328Replicating a Build Offline
4329--------------------------- 4329---------------------------
@@ -4597,7 +4597,7 @@ how the static library files are defined::
4597 PACKAGES_DYNAMIC = "^${PN}-locale-.*" 4597 PACKAGES_DYNAMIC = "^${PN}-locale-.*"
4598 FILES = "" 4598 FILES = ""
4599 4599
4600 FILES_${PN} = "${bindir}/* ${sbindir}/* ${libexecdir}/* ${libdir}/lib*${SOLIBS} \ 4600 FILES:${PN} = "${bindir}/* ${sbindir}/* ${libexecdir}/* ${libdir}/lib*${SOLIBS} \
4601 ${sysconfdir} ${sharedstatedir} ${localstatedir} \ 4601 ${sysconfdir} ${sharedstatedir} ${localstatedir} \
4602 ${base_bindir}/* ${base_sbindir}/* \ 4602 ${base_bindir}/* ${base_sbindir}/* \
4603 ${base_libdir}/*${SOLIBS} \ 4603 ${base_libdir}/*${SOLIBS} \
@@ -4607,24 +4607,24 @@ how the static library files are defined::
4607 ${datadir}/idl ${datadir}/omf ${datadir}/sounds \ 4607 ${datadir}/idl ${datadir}/omf ${datadir}/sounds \
4608 ${libdir}/bonobo/servers" 4608 ${libdir}/bonobo/servers"
4609 4609
4610 FILES_${PN}-bin = "${bindir}/* ${sbindir}/*" 4610 FILES:${PN}-bin = "${bindir}/* ${sbindir}/*"
4611 4611
4612 FILES_${PN}-doc = "${docdir} ${mandir} ${infodir} ${datadir}/gtk-doc \ 4612 FILES:${PN}-doc = "${docdir} ${mandir} ${infodir} ${datadir}/gtk-doc \
4613 ${datadir}/gnome/help" 4613 ${datadir}/gnome/help"
4614 SECTION_${PN}-doc = "doc" 4614 SECTION:${PN}-doc = "doc"
4615 4615
4616 FILES_SOLIBSDEV ?= "${base_libdir}/lib*${SOLIBSDEV} ${libdir}/lib*${SOLIBSDEV}" 4616 FILES_SOLIBSDEV ?= "${base_libdir}/lib*${SOLIBSDEV} ${libdir}/lib*${SOLIBSDEV}"
4617 FILES_${PN}-dev = "${includedir} ${FILES_SOLIBSDEV} ${libdir}/*.la \ 4617 FILES:${PN}-dev = "${includedir} ${FILES_SOLIBSDEV} ${libdir}/*.la \
4618 ${libdir}/*.o ${libdir}/pkgconfig ${datadir}/pkgconfig \ 4618 ${libdir}/*.o ${libdir}/pkgconfig ${datadir}/pkgconfig \
4619 ${datadir}/aclocal ${base_libdir}/*.o \ 4619 ${datadir}/aclocal ${base_libdir}/*.o \
4620 ${libdir}/${BPN}/*.la ${base_libdir}/*.la" 4620 ${libdir}/${BPN}/*.la ${base_libdir}/*.la"
4621 SECTION_${PN}-dev = "devel" 4621 SECTION:${PN}-dev = "devel"
4622 ALLOW_EMPTY_${PN}-dev = "1" 4622 ALLOW_EMPTY:${PN}-dev = "1"
4623 RDEPENDS_${PN}-dev = "${PN} (= ${EXTENDPKGV})" 4623 RDEPENDS:${PN}-dev = "${PN} (= ${EXTENDPKGV})"
4624 4624
4625 FILES_${PN}-staticdev = "${libdir}/*.a ${base_libdir}/*.a ${libdir}/${BPN}/*.a" 4625 FILES:${PN}-staticdev = "${libdir}/*.a ${base_libdir}/*.a ${libdir}/${BPN}/*.a"
4626 SECTION_${PN}-staticdev = "devel" 4626 SECTION:${PN}-staticdev = "devel"
4627 RDEPENDS_${PN}-staticdev = "${PN}-dev (= ${EXTENDPKGV})" 4627 RDEPENDS:${PN}-staticdev = "${PN}-dev (= ${EXTENDPKGV})"
4628 4628
4629Combining Multiple Versions of Library Files into One Image 4629Combining Multiple Versions of Library Files into One Image
4630----------------------------------------------------------- 4630-----------------------------------------------------------
@@ -4701,8 +4701,8 @@ configuration would be as follows::
4701 MACHINE = "qemux86-64" 4701 MACHINE = "qemux86-64"
4702 require conf/multilib.conf 4702 require conf/multilib.conf
4703 MULTILIBS = "multilib:lib32" 4703 MULTILIBS = "multilib:lib32"
4704 DEFAULTTUNE_virtclass-multilib-lib32 = "x86" 4704 DEFAULTTUNE:virtclass-multilib-lib32 = "x86"
4705 IMAGE_INSTALL_append = "lib32-glib-2.0" 4705 IMAGE_INSTALL:append = "lib32-glib-2.0"
4706 4706
4707This example enables an additional library named 4707This example enables an additional library named
4708``lib32`` alongside the normal target packages. When combining these 4708``lib32`` alongside the normal target packages. When combining these
@@ -4749,7 +4749,7 @@ Here are the implementation details for the RPM Package Management System:
4749 :term:`Build Directory`. For 4749 :term:`Build Directory`. For
4750 example, consider ``lib32`` in a ``qemux86-64`` image. The possible 4750 example, consider ``lib32`` in a ``qemux86-64`` image. The possible
4751 architectures in the system are "all", "qemux86_64", 4751 architectures in the system are "all", "qemux86_64",
4752 "lib32_qemux86_64", and "lib32_x86". 4752 "lib32:qemux86_64", and "lib32:x86".
4753 4753
4754- The ``${MLPREFIX}`` variable is stripped from ``${PN}`` during RPM 4754- The ``${MLPREFIX}`` variable is stripped from ``${PN}`` during RPM
4755 packaging. The naming for a normal RPM package and a Multilib RPM 4755 packaging. The naming for a normal RPM package and a Multilib RPM
@@ -4768,7 +4768,7 @@ Here are the implementation details for the IPK Package Management System:
4768- The ``${MLPREFIX}`` is not stripped from ``${PN}`` during IPK 4768- The ``${MLPREFIX}`` is not stripped from ``${PN}`` during IPK
4769 packaging. The naming for a normal RPM package and a Multilib IPK 4769 packaging. The naming for a normal RPM package and a Multilib IPK
4770 package in a ``qemux86-64`` system resolves to something like 4770 package in a ``qemux86-64`` system resolves to something like
4771 ``bash_4.1-r2.x86_64.ipk`` and ``lib32-bash_4.1-rw_x86.ipk``, 4771 ``bash_4.1-r2.x86_64.ipk`` and ``lib32-bash_4.1-rw:x86.ipk``,
4772 respectively. 4772 respectively.
4773 4773
4774- The IPK deploy folder is not modified with ``${MLPREFIX}`` because 4774- The IPK deploy folder is not modified with ``${MLPREFIX}`` because
@@ -4857,7 +4857,7 @@ configuration file as follows::
4857 4857
4858 MACHINE = "qemux86-64" 4858 MACHINE = "qemux86-64"
4859 DEFAULTTUNE = "x86-64-x32" 4859 DEFAULTTUNE = "x86-64-x32"
4860 baselib = "${@d.getVar('BASE_LIB_tune-' + (d.getVar('DEFAULTTUNE') \ 4860 baselib = "${@d.getVar('BASE_LIB:tune-' + (d.getVar('DEFAULTTUNE') \
4861 or 'INVALID')) or 'lib'}" 4861 or 'INVALID')) or 'lib'}"
4862 4862
4863Once you have set 4863Once you have set
@@ -6514,7 +6514,7 @@ setting 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 () {
6518 lighttpd_libdir = d.expand('${libdir}') 6518 lighttpd_libdir = d.expand('${libdir}')
6519 do_split_packages(d, lighttpd_libdir, '^mod_(.*).so$', 6519 do_split_packages(d, lighttpd_libdir, '^mod_(.*).so$',
6520 'lighttpd-module-%s', 'Lighttpd module for %s', 6520 'lighttpd-module-%s', 'Lighttpd module for %s',
@@ -7101,7 +7101,7 @@ To add package testing to your build, add the
7101variables to your ``local.conf`` file, which is found in the 7101variables to your ``local.conf`` file, which is found in the
7102:term:`Build Directory`:: 7102:term:`Build Directory`::
7103 7103
7104 DISTRO_FEATURES_append = " ptest" 7104 DISTRO_FEATURES:append = " ptest"
7105 EXTRA_IMAGE_FEATURES += "ptest-pkgs" 7105 EXTRA_IMAGE_FEATURES += "ptest-pkgs"
7106 7106
7107Once your build is complete, the ptest files are installed into the 7107Once your build is complete, the ptest files are installed into the
@@ -7145,7 +7145,7 @@ test. Here is what you have to do for each recipe:
7145 your recipe in order for the package to meet the dependencies. Here 7145 your recipe in order for the package to meet the dependencies. Here
7146 is an example where the package has a runtime dependency on "make":: 7146 is an example where the package has a runtime dependency on "make"::
7147 7147
7148 RDEPENDS_${PN}-ptest += "make" 7148 RDEPENDS:${PN}-ptest += "make"
7149 7149
7150- *Add a function to build the test suite:* Not many packages support 7150- *Add a function to build the test suite:* Not many packages support
7151 cross-compilation of their test suites. Consequently, you usually 7151 cross-compilation of their test suites. Consequently, you usually
@@ -7289,11 +7289,11 @@ The ``devtool edit-recipe`` command lets you take a look at the recipe::
7289 " 7289 "
7290 S = "${WORKDIR}/npm" 7290 S = "${WORKDIR}/npm"
7291 inherit npm 7291 inherit npm
7292 LICENSE_${PN} = "MIT" 7292 LICENSE:${PN} = "MIT"
7293 LICENSE_${PN}-accepts = "MIT" 7293 LICENSE:${PN}-accepts = "MIT"
7294 LICENSE_${PN}-array-flatten = "MIT" 7294 LICENSE:${PN}-array-flatten = "MIT"
7295 ... 7295 ...
7296 LICENSE_${PN}-vary = "MIT" 7296 LICENSE:${PN}-vary = "MIT"
7297 7297
7298Here are three key points in the previous example: 7298Here are three key points in the previous example:
7299 7299
@@ -7523,7 +7523,7 @@ Using systemd Exclusively
7523 7523
7524Set these variables in your distribution configuration file as follows:: 7524Set these variables in your distribution configuration file as follows::
7525 7525
7526 DISTRO_FEATURES_append = " systemd" 7526 DISTRO_FEATURES:append = " systemd"
7527 VIRTUAL-RUNTIME_init_manager = "systemd" 7527 VIRTUAL-RUNTIME_init_manager = "systemd"
7528 7528
7529You can also prevent the SysVinit distribution feature from 7529You can also prevent the SysVinit distribution feature from
@@ -7547,7 +7547,7 @@ Using systemd for the Main Image and Using SysVinit for the Rescue Image
7547 7547
7548Set these variables in your distribution configuration file as follows:: 7548Set these variables in your distribution configuration file as follows::
7549 7549
7550 DISTRO_FEATURES_append = " systemd" 7550 DISTRO_FEATURES:append = " systemd"
7551 VIRTUAL-RUNTIME_init_manager = "systemd" 7551 VIRTUAL-RUNTIME_init_manager = "systemd"
7552 7552
7553Doing so causes your main image to use the 7553Doing so causes your main image to use the
@@ -7646,7 +7646,7 @@ the recipe needs to reference
7646Then, you can add the following to your 7646Then, you can add the following to your
7647``local.conf``:: 7647``local.conf``::
7648 7648
7649 SRCREV_pn-PN = "${AUTOREV}" 7649 SRCREV:pn-PN = "${AUTOREV}"
7650 7650
7651:term:`PN` is the name of the recipe for 7651:term:`PN` is the name of the recipe for
7652which you want to enable automatic source revision updating. 7652which you want to enable automatic source revision updating.
@@ -7669,17 +7669,17 @@ listed include file that contains numerous lines of exactly that form::
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}"
7675 SRCREV_pn-matchbox-desktop ?= "${AUTOREV}" 7675 SRCREV:pn-matchbox-desktop ?= "${AUTOREV}"
7676 SRCREV_pn-matchbox-keyboard ?= "${AUTOREV}" 7676 SRCREV:pn-matchbox-keyboard ?= "${AUTOREV}"
7677 SRCREV_pn-matchbox-panel-2 ?= "${AUTOREV}" 7677 SRCREV:pn-matchbox-panel-2 ?= "${AUTOREV}"
7678 SRCREV_pn-matchbox-themes-extra ?= "${AUTOREV}" 7678 SRCREV:pn-matchbox-themes-extra ?= "${AUTOREV}"
7679 SRCREV_pn-matchbox-terminal ?= "${AUTOREV}" 7679 SRCREV:pn-matchbox-terminal ?= "${AUTOREV}"
7680 SRCREV_pn-matchbox-wm ?= "${AUTOREV}" 7680 SRCREV:pn-matchbox-wm ?= "${AUTOREV}"
7681 SRCREV_pn-settings-daemon ?= "${AUTOREV}" 7681 SRCREV:pn-settings-daemon ?= "${AUTOREV}"
7682 SRCREV_pn-screenshot ?= "${AUTOREV}" 7682 SRCREV:pn-screenshot ?= "${AUTOREV}"
7683 . . . 7683 . . .
7684 7684
7685These lines allow you to 7685These lines allow you to
@@ -7922,25 +7922,25 @@ output from this command::
7922 7922
7923 $ buildhistory-collect-srcrevs -a 7923 $ buildhistory-collect-srcrevs -a
7924 # i586-poky-linux 7924 # i586-poky-linux
7925 SRCREV_pn-glibc = "b8079dd0d360648e4e8de48656c5c38972621072" 7925 SRCREV:pn-glibc = "b8079dd0d360648e4e8de48656c5c38972621072"
7926 SRCREV_pn-glibc-initial = "b8079dd0d360648e4e8de48656c5c38972621072" 7926 SRCREV:pn-glibc-initial = "b8079dd0d360648e4e8de48656c5c38972621072"
7927 SRCREV_pn-opkg-utils = "53274f087565fd45d8452c5367997ba6a682a37a" 7927 SRCREV:pn-opkg-utils = "53274f087565fd45d8452c5367997ba6a682a37a"
7928 SRCREV_pn-kmod = "fd56638aed3fe147015bfa10ed4a5f7491303cb4" 7928 SRCREV:pn-kmod = "fd56638aed3fe147015bfa10ed4a5f7491303cb4"
7929 # x86_64-linux 7929 # x86_64-linux
7930 SRCREV_pn-gtk-doc-stub-native = "1dea266593edb766d6d898c79451ef193eb17cfa" 7930 SRCREV:pn-gtk-doc-stub-native = "1dea266593edb766d6d898c79451ef193eb17cfa"
7931 SRCREV_pn-dtc-native = "65cc4d2748a2c2e6f27f1cf39e07a5dbabd80ebf" 7931 SRCREV:pn-dtc-native = "65cc4d2748a2c2e6f27f1cf39e07a5dbabd80ebf"
7932 SRCREV_pn-update-rc.d-native = "eca680ddf28d024954895f59a241a622dd575c11" 7932 SRCREV:pn-update-rc.d-native = "eca680ddf28d024954895f59a241a622dd575c11"
7933 SRCREV_glibc_pn-cross-localedef-native = "b8079dd0d360648e4e8de48656c5c38972621072" 7933 SRCREV_glibc:pn-cross-localedef-native = "b8079dd0d360648e4e8de48656c5c38972621072"
7934 SRCREV_localedef_pn-cross-localedef-native = "c833367348d39dad7ba018990bfdaffaec8e9ed3" 7934 SRCREV_localedef:pn-cross-localedef-native = "c833367348d39dad7ba018990bfdaffaec8e9ed3"
7935 SRCREV_pn-prelink-native = "faa069deec99bf61418d0bab831c83d7c1b797ca" 7935 SRCREV:pn-prelink-native = "faa069deec99bf61418d0bab831c83d7c1b797ca"
7936 SRCREV_pn-opkg-utils-native = "53274f087565fd45d8452c5367997ba6a682a37a" 7936 SRCREV:pn-opkg-utils-native = "53274f087565fd45d8452c5367997ba6a682a37a"
7937 SRCREV_pn-kern-tools-native = "23345b8846fe4bd167efdf1bd8a1224b2ba9a5ff" 7937 SRCREV:pn-kern-tools-native = "23345b8846fe4bd167efdf1bd8a1224b2ba9a5ff"
7938 SRCREV_pn-kmod-native = "fd56638aed3fe147015bfa10ed4a5f7491303cb4" 7938 SRCREV:pn-kmod-native = "fd56638aed3fe147015bfa10ed4a5f7491303cb4"
7939 # qemux86-poky-linux 7939 # qemux86-poky-linux
7940 SRCREV_machine_pn-linux-yocto = "38cd560d5022ed2dbd1ab0dca9642e47c98a0aa1" 7940 SRCREV_machine:pn-linux-yocto = "38cd560d5022ed2dbd1ab0dca9642e47c98a0aa1"
7941 SRCREV_meta_pn-linux-yocto = "a227f20eff056e511d504b2e490f3774ab260d6f" 7941 SRCREV_meta:pn-linux-yocto = "a227f20eff056e511d504b2e490f3774ab260d6f"
7942 # all-poky-linux 7942 # all-poky-linux
7943 SRCREV_pn-update-rc.d = "eca680ddf28d024954895f59a241a622dd575c11" 7943 SRCREV:pn-update-rc.d = "eca680ddf28d024954895f59a241a622dd575c11"
7944 7944
7945.. note:: 7945.. note::
7946 7946
@@ -8564,11 +8564,11 @@ Here are some things to keep in mind when running tests:
8564 8564
8565- The default tests for the image are defined as:: 8565- The default tests for the image are defined as::
8566 8566
8567 DEFAULT_TEST_SUITES_pn-image = "ping ssh df connman syslog xorg scp vnc date rpm dnf dmesg" 8567 DEFAULT_TEST_SUITES:pn-image = "ping ssh df connman syslog xorg scp vnc date rpm dnf dmesg"
8568 8568
8569- Add your own test to the list of the by using the following:: 8569- Add your own test to the list of the by using the following::
8570 8570
8571 TEST_SUITES_append = " mytest" 8571 TEST_SUITES:append = " mytest"
8572 8572
8573- Run a specific list of tests as follows:: 8573- Run a specific list of tests as follows::
8574 8574
@@ -9715,7 +9715,7 @@ To run a ``debuginfod`` server, you need to do the following:
9715 (it already is in ``OpenEmbedded-core`` defaults and ``poky`` reference distribution). 9715 (it already is in ``OpenEmbedded-core`` defaults and ``poky`` reference distribution).
9716 If not, set in your distro config file or in ``local.conf``:: 9716 If not, set in your distro config file or in ``local.conf``::
9717 9717
9718 DISTRO_FEATURES_append = " debuginfod" 9718 DISTRO_FEATURES:append = " debuginfod"
9719 9719
9720 This distro feature enables the server and client library in ``elfutils``, 9720 This distro feature enables the server and client library in ``elfutils``,
9721 and enables ``debuginfod`` support in clients (at the moment, ``gdb`` and ``binutils``). 9721 and enables ``debuginfod`` support in clients (at the moment, ``gdb`` and ``binutils``).
@@ -9802,7 +9802,7 @@ debugger.
9802 Make the following addition in either your ``local.conf`` file or in 9802 Make the following addition in either your ``local.conf`` file or in
9803 an image recipe:: 9803 an image recipe::
9804 9804
9805 IMAGE_INSTALL_append = " gdbserver" 9805 IMAGE_INSTALL:append = " gdbserver"
9806 9806
9807 The change makes 9807 The change makes
9808 sure the ``gdbserver`` package is included. 9808 sure the ``gdbserver`` package is included.
@@ -9938,21 +9938,21 @@ To support this kind of debugging, you need do the following:
9938- Ensure that GDB is on the target. You can do this by adding "gdb" to 9938- Ensure that GDB is on the target. You can do this by adding "gdb" to
9939 :term:`IMAGE_INSTALL`:: 9939 :term:`IMAGE_INSTALL`::
9940 9940
9941 IMAGE_INSTALL_append = " gdb" 9941 IMAGE_INSTALL:append = " gdb"
9942 9942
9943 Alternatively, you can add "tools-debug" to :term:`IMAGE_FEATURES`:: 9943 Alternatively, you can add "tools-debug" to :term:`IMAGE_FEATURES`::
9944 9944
9945 IMAGE_FEATURES_append = " tools-debug" 9945 IMAGE_FEATURES:append = " tools-debug"
9946 9946
9947- Ensure that debug symbols are present. You can make sure these 9947- Ensure that debug symbols are present. You can make sure these
9948 symbols are present by installing ``-dbg``:: 9948 symbols are present by installing ``-dbg``::
9949 9949
9950 IMAGE_INSTALL_append = "packagename-dbg" 9950 IMAGE_INSTALL:append = "packagename-dbg"
9951 9951
9952 Alternatively, you can do the following to include 9952 Alternatively, you can do the following to include
9953 all the debug symbols:: 9953 all the debug symbols::
9954 9954
9955 IMAGE_FEATURES_append = " dbg-pkgs" 9955 IMAGE_FEATURES:append = " dbg-pkgs"
9956 9956
9957.. note:: 9957.. note::
9958 9958
@@ -11343,7 +11343,7 @@ support, include the "wayland" flag in the
11343:term:`DISTRO_FEATURES` 11343:term:`DISTRO_FEATURES`
11344statement in your ``local.conf`` file:: 11344statement in your ``local.conf`` file::
11345 11345
11346 DISTRO_FEATURES_append = " wayland" 11346 DISTRO_FEATURES:append = " wayland"
11347 11347
11348.. note:: 11348.. note::
11349 11349