summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.xml21
-rw-r--r--documentation/dev-manual/dev-manual-start.xml19
-rw-r--r--documentation/ref-manual/faq.xml2
-rw-r--r--documentation/ref-manual/introduction.xml7
-rw-r--r--documentation/ref-manual/migration.xml17
-rw-r--r--documentation/ref-manual/ref-classes.xml13
-rw-r--r--documentation/ref-manual/ref-variables.xml72
-rw-r--r--documentation/ref-manual/technical-details.xml18
8 files changed, 98 insertions, 71 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index e0db037454..ba182acaf4 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -3603,10 +3603,11 @@
3603 <title>Additional Implementation Details</title> 3603 <title>Additional Implementation Details</title>
3604 3604
3605 <para> 3605 <para>
3606 Different packaging systems have different levels of native Multilib 3606 Different packaging systems have different levels of
3607 support. 3607 native Multilib support (i.e. support for the host build
3608 For the RPM Package Management System, the following implementation details 3608 machine).
3609 exist: 3609 For the RPM Package Management System, the following
3610 implementation details exist:
3610 <itemizedlist> 3611 <itemizedlist>
3611 <listitem><para>A unique architecture is defined for the Multilib packages, 3612 <listitem><para>A unique architecture is defined for the Multilib packages,
3612 along with creating a unique deploy folder under 3613 along with creating a unique deploy folder under
@@ -3823,7 +3824,8 @@
3823 in the form generated by the build system. 3824 in the form generated by the build system.
3824 </para></listitem> 3825 </para></listitem>
3825 <listitem><para> 3826 <listitem><para>
3826 You must build several native tools: 3827 You must build several native tools, which are tools
3828 built to run on the build system:
3827 <literallayout class='monospaced'> 3829 <literallayout class='monospaced'>
3828 $ bitbake parted-native dosfstools-native mtools-native 3830 $ bitbake parted-native dosfstools-native mtools-native
3829 </literallayout> 3831 </literallayout>
@@ -6375,8 +6377,9 @@
6375 developers when building for multiple machines. 6377 developers when building for multiple machines.
6376 When you use the same <filename>TMPDIR</filename> for 6378 When you use the same <filename>TMPDIR</filename> for
6377 multiple machine builds, the OpenEmbedded build system can 6379 multiple machine builds, the OpenEmbedded build system can
6378 reuse the existing native and often cross-recipes for 6380 reuse the existing native (i.e. host system) and often
6379 multiple machines. 6381 cross-recipes (i.e. <filename>nativesdk</filename>
6382 for multiple machines.
6380 Thus, build time decreases. 6383 Thus, build time decreases.
6381 <note> 6384 <note>
6382 If 6385 If
@@ -7583,6 +7586,7 @@
7583 run the test suite by using a single command 7586 run the test suite by using a single command
7584 such as <filename>make check</filename>. 7587 such as <filename>make check</filename>.
7585 However, the native <filename>make check</filename> 7588 However, the native <filename>make check</filename>
7589 that runs on the host system
7586 builds and runs on the same computer, while 7590 builds and runs on the same computer, while
7587 cross-compiling requires that the package is built 7591 cross-compiling requires that the package is built
7588 on the host but executed on the target. 7592 on the host but executed on the target.
@@ -8169,7 +8173,8 @@
8169 specific to or dependent on the target 8173 specific to or dependent on the target
8170 architecture:</emphasis> 8174 architecture:</emphasis>
8171 You can work around these attempts by using native 8175 You can work around these attempts by using native
8172 tools to accomplish the same tasks, or 8176 tools, which run on the host system,
8177 to accomplish the same tasks, or
8173 by alternatively running the processes under QEMU, 8178 by alternatively running the processes under QEMU,
8174 which has the <filename>qemu_run_binary</filename> 8179 which has the <filename>qemu_run_binary</filename>
8175 function. 8180 function.
diff --git a/documentation/dev-manual/dev-manual-start.xml b/documentation/dev-manual/dev-manual-start.xml
index db989b7bfa..9f349adcdd 100644
--- a/documentation/dev-manual/dev-manual-start.xml
+++ b/documentation/dev-manual/dev-manual-start.xml
@@ -341,14 +341,17 @@
341 </para> 341 </para>
342 342
343 <para> 343 <para>
344 Using a pre-built binary is ideal for developing software applications to run on your 344 Using a pre-built binary is ideal for developing software
345 target hardware. 345 applications to run on your target hardware.
346 To do this, you need to be able to access the appropriate cross-toolchain tarball for 346 To do this, you need to be able to access the appropriate
347 the architecture on which you are developing. 347 cross-toolchain tarball for the architecture on which you are
348 If you are using an SDK type image, the image ships with the complete toolchain native to 348 developing.
349 the architecture. 349 If you are using an SDK type image, the image ships with the complete
350 If you are not using an SDK type image, you need to separately download and 350 toolchain native to the architecture (i.e. a toolchain designed to
351 install the stand-alone Yocto Project cross-toolchain tarball. 351 run on the
352 <ulink url='&YOCTO_DOCS_REF_URL;#var-SDKMACHINE'><filename>SDKMACHINE</filename></ulink>).
353 If you are not using an SDK type image, you need to separately download
354 and install the stand-alone Yocto Project cross-toolchain tarball.
352 </para> 355 </para>
353 356
354 <para> 357 <para>
diff --git a/documentation/ref-manual/faq.xml b/documentation/ref-manual/faq.xml
index 08e0fb170b..3137639d9a 100644
--- a/documentation/ref-manual/faq.xml
+++ b/documentation/ref-manual/faq.xml
@@ -791,7 +791,7 @@
791 <qandaentry> 791 <qandaentry>
792 <question> 792 <question>
793 <para> 793 <para>
794 The files provided by my <filename>-native</filename> recipe do 794 The files provided by my <filename>*-native</filename> recipe do
795 not appear to be available to other recipes. 795 not appear to be available to other recipes.
796 Files are missing from the native sysroot, my recipe is 796 Files are missing from the native sysroot, my recipe is
797 installing to the wrong place, or I am getting permissions 797 installing to the wrong place, or I am getting permissions
diff --git a/documentation/ref-manual/introduction.xml b/documentation/ref-manual/introduction.xml
index 57e4a25853..750d9c681c 100644
--- a/documentation/ref-manual/introduction.xml
+++ b/documentation/ref-manual/introduction.xml
@@ -450,7 +450,9 @@
450 $ sh poky-glibc-x86_64-buildtools-tarball-x86_64-buildtools-nativesdk-standalone-&DISTRO;.sh 450 $ sh poky-glibc-x86_64-buildtools-tarball-x86_64-buildtools-nativesdk-standalone-&DISTRO;.sh
451 </literallayout> 451 </literallayout>
452 During execution, a prompt appears that allows you to 452 During execution, a prompt appears that allows you to
453 choose the installation directory. 453 choose the installation directory for these tools
454 designed to run on the target machine
455 (<link linkend='var-SDKMACHINE'><filename>SDKMACHINE</filename></link>).
454 For example, you could choose the following: 456 For example, you could choose the following:
455 <literallayout class='monospaced'> 457 <literallayout class='monospaced'>
456 /home/<replaceable>your-username</replaceable>/buildtools 458 /home/<replaceable>your-username</replaceable>/buildtools
@@ -530,7 +532,8 @@
530 <listitem><para> 532 <listitem><para>
531 On the machine that does not meet the requirements, 533 On the machine that does not meet the requirements,
532 run the <filename>.sh</filename> file 534 run the <filename>.sh</filename> file
533 to install the tools. 535 to install the tools built to run on the target machine
536 (<link linkend='var-SDKMACHINE'><filename>SDKMACHINE</filename></link>).
534 Here is an example: 537 Here is an example:
535 <literallayout class='monospaced'> 538 <literallayout class='monospaced'>
536 $ sh poky-glibc-x86_64-buildtools-tarball-x86_64-buildtools-nativesdk-standalone-&DISTRO;.sh 539 $ sh poky-glibc-x86_64-buildtools-tarball-x86_64-buildtools-nativesdk-standalone-&DISTRO;.sh
diff --git a/documentation/ref-manual/migration.xml b/documentation/ref-manual/migration.xml
index 45ac041d92..62f792bf7b 100644
--- a/documentation/ref-manual/migration.xml
+++ b/documentation/ref-manual/migration.xml
@@ -97,13 +97,14 @@
97 97
98 <para> 98 <para>
99 The shared state cache (sstate-cache), as pointed to by 99 The shared state cache (sstate-cache), as pointed to by
100 <link linkend='var-SSTATE_DIR'><filename>SSTATE_DIR</filename></link>, by default 100 <link linkend='var-SSTATE_DIR'><filename>SSTATE_DIR</filename></link>,
101 now has two-character subdirectories to prevent issues arising 101 by default now has two-character subdirectories to prevent
102 from too many files in the same directory. 102 issues arising from too many files in the same directory.
103 Also, native sstate-cache packages will go into a subdirectory named using 103 Also, native sstate-cache packages, which are built to run
104 on the host system, will go into a subdirectory named using
104 the distro ID string. 105 the distro ID string.
105 If you copy the newly structured sstate-cache to a mirror location 106 If you copy the newly structured sstate-cache to a mirror
106 (either local or remote) and then point to it in 107 location (either local or remote) and then point to it in
107 <link linkend='var-SSTATE_MIRRORS'><filename>SSTATE_MIRRORS</filename></link>, 108 <link linkend='var-SSTATE_MIRRORS'><filename>SSTATE_MIRRORS</filename></link>,
108 you need to append "PATH" to the end of the mirror URL so that 109 you need to append "PATH" to the end of the mirror URL so that
109 the path used by BitBake before the mirror substitution is 110 the path used by BitBake before the mirror substitution is
@@ -191,7 +192,9 @@
191 The suffix <filename>nativesdk</filename> is now implemented 192 The suffix <filename>nativesdk</filename> is now implemented
192 as a prefix, which simplifies a lot of the packaging code for 193 as a prefix, which simplifies a lot of the packaging code for
193 <filename>nativesdk</filename> recipes. 194 <filename>nativesdk</filename> recipes.
194 All custom <filename>nativesdk</filename> recipes and any 195 All custom <filename>nativesdk</filename> recipes, which are
196 recipes built on the host system to create packages for the
197 target machine, and any
195 references need to be updated to use 198 references need to be updated to use
196 <filename>nativesdk-*</filename> instead of 199 <filename>nativesdk-*</filename> instead of
197 <filename>*-nativesdk</filename>. 200 <filename>*-nativesdk</filename>.
diff --git a/documentation/ref-manual/ref-classes.xml b/documentation/ref-manual/ref-classes.xml
index 7ba9a9770f..f994a2269d 100644
--- a/documentation/ref-manual/ref-classes.xml
+++ b/documentation/ref-manual/ref-classes.xml
@@ -463,10 +463,11 @@
463 463
464 <para> 464 <para>
465 The <filename>chrpath</filename> class 465 The <filename>chrpath</filename> class
466 is a wrapper around the "chrpath" utility, which is used during the 466 is a wrapper around the "chrpath" utility.
467 build process for <filename>nativesdk</filename>, 467 This utility is used during the build process for
468 <filename>cross</filename>, and 468 <filename>nativesdk</filename>, <filename>cross</filename>, and
469 <filename>cross-canadian</filename> recipes to change 469 <filename>cross-canadian</filename> recipes, which run on the host
470 system to create packages for the target hardware and change
470 <filename>RPATH</filename> records within binaries in order to make 471 <filename>RPATH</filename> records within binaries in order to make
471 them relocatable. 472 them relocatable.
472 </para> 473 </para>
@@ -1146,8 +1147,8 @@
1146 <title><filename>gzipnative.bbclass</filename></title> 1147 <title><filename>gzipnative.bbclass</filename></title>
1147 1148
1148 <para> 1149 <para>
1149 The <filename>gzipnative</filename> 1150 The <filename>gzipnative</filename> class enables the use of
1150 class enables the use of native versions of <filename>gzip</filename> 1151 different native versions of <filename>gzip</filename>
1151 and <filename>pigz</filename> rather than the versions of these tools 1152 and <filename>pigz</filename> rather than the versions of these tools
1152 from the build host. 1153 from the build host.
1153 </para> 1154 </para>
diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml
index 4ca4e51d5d..71f4ca680c 100644
--- a/documentation/ref-manual/ref-variables.xml
+++ b/documentation/ref-manual/ref-variables.xml
@@ -1396,15 +1396,22 @@
1396 <para role="glossdeffirst"> 1396 <para role="glossdeffirst">
1397<!-- <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> --> 1397<!-- <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> -->
1398 The bare name of the recipe. 1398 The bare name of the recipe.
1399 This variable is a version of the <link linkend='var-PN'><filename>PN</filename></link> variable 1399 This variable is a version of the
1400 but removes common suffixes such as "-native" and "-cross" as well 1400 <link linkend='var-PN'><filename>PN</filename></link>
1401 as removes common prefixes such as multilib's "lib64-" and "lib32-". 1401 variable but removes common suffixes such as
1402 <filename>-native</filename> and
1403 <filename>-cross</filename> as well
1404 as removes common prefixes such as multilib's
1405 <filename>lib64-</filename> and
1406 <filename>lib32-</filename>.
1402 The exact list of suffixes removed is specified by the 1407 The exact list of suffixes removed is specified by the
1403 <link linkend='var-SPECIAL_PKGSUFFIX'><filename>SPECIAL_PKGSUFFIX</filename></link> variable. 1408 <link linkend='var-SPECIAL_PKGSUFFIX'><filename>SPECIAL_PKGSUFFIX</filename></link>
1409 variable.
1404 The exact list of prefixes removed is specified by the 1410 The exact list of prefixes removed is specified by the
1405 <link linkend='var-MLPREFIX'><filename>MLPREFIX</filename></link> variable. 1411 <link linkend='var-MLPREFIX'><filename>MLPREFIX</filename></link>
1412 variable.
1406 Prefixes are removed for <filename>multilib</filename> 1413 Prefixes are removed for <filename>multilib</filename>
1407 and <filename>nativesdk</filename> cases. 1414 and <filename>nativesdk-</filename> cases.
1408 </para> 1415 </para>
1409 </glossdef> 1416 </glossdef>
1410 </glossentry> 1417 </glossentry>
@@ -1467,7 +1474,7 @@
1467 Specifies the flags to pass to the C pre-processor 1474 Specifies the flags to pass to the C pre-processor
1468 (i.e. to both the C and the C++ compilers) when building 1475 (i.e. to both the C and the C++ compilers) when building
1469 for the build host. 1476 for the build host.
1470 When building in the <filename>native</filename> context, 1477 When building in the <filename>-native</filename> context,
1471 <link linkend='var-CPPFLAGS'><filename>CPPFLAGS</filename></link> 1478 <link linkend='var-CPPFLAGS'><filename>CPPFLAGS</filename></link>
1472 is set to the value of this variable by default. 1479 is set to the value of this variable by default.
1473 </para> 1480 </para>
@@ -1483,7 +1490,7 @@
1483<!-- <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> --> 1490<!-- <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> -->
1484 Specifies the flags to pass to the C++ compiler when 1491 Specifies the flags to pass to the C++ compiler when
1485 building for the build host. 1492 building for the build host.
1486 When building in the <filename>native</filename> context, 1493 When building in the <filename>-native</filename> context,
1487 <link linkend='var-CXXFLAGS'><filename>CXXFLAGS</filename></link> 1494 <link linkend='var-CXXFLAGS'><filename>CXXFLAGS</filename></link>
1488 is set to the value of this variable by default. 1495 is set to the value of this variable by default.
1489 </para> 1496 </para>
@@ -1558,7 +1565,7 @@
1558 The OpenEmbedded build system uses the 1565 The OpenEmbedded build system uses the
1559 <filename>BUILD_PREFIX</filename> value to set the 1566 <filename>BUILD_PREFIX</filename> value to set the
1560 <link linkend='var-TARGET_PREFIX'><filename>TARGET_PREFIX</filename></link> 1567 <link linkend='var-TARGET_PREFIX'><filename>TARGET_PREFIX</filename></link>
1561 when building for native recipes. 1568 when building for <filename>native</filename> recipes.
1562 </para> 1569 </para>
1563 </glossdef> 1570 </glossdef>
1564 </glossentry> 1571 </glossentry>
@@ -1839,7 +1846,7 @@
1839<!-- <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> --> 1846<!-- <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> -->
1840 Specifies the flags to pass to the C compiler when building 1847 Specifies the flags to pass to the C compiler when building
1841 for the SDK. 1848 for the SDK.
1842 When building in the <filename>nativesdk</filename> 1849 When building in the <filename>nativesdk-</filename>
1843 context, 1850 context,
1844 <link linkend='var-CFLAGS'><filename>CFLAGS</filename></link> 1851 <link linkend='var-CFLAGS'><filename>CFLAGS</filename></link>
1845 is set to the value of this variable by default. 1852 is set to the value of this variable by default.
@@ -1857,7 +1864,7 @@
1857 Specifies the flags to pass to the C pre-processor 1864 Specifies the flags to pass to the C pre-processor
1858 (i.e. to both the C and the C++ compilers) when building 1865 (i.e. to both the C and the C++ compilers) when building
1859 for the SDK. 1866 for the SDK.
1860 When building in the <filename>nativesdk</filename> 1867 When building in the <filename>nativesdk-</filename>
1861 context, 1868 context,
1862 <link linkend='var-CPPFLAGS'><filename>CPPFLAGS</filename></link> 1869 <link linkend='var-CPPFLAGS'><filename>CPPFLAGS</filename></link>
1863 is set to the value of this variable by default. 1870 is set to the value of this variable by default.
@@ -1874,7 +1881,7 @@
1874<!-- <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> --> 1881<!-- <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> -->
1875 Specifies the flags to pass to the C++ compiler when 1882 Specifies the flags to pass to the C++ compiler when
1876 building for the SDK. 1883 building for the SDK.
1877 When building in the <filename>nativesdk</filename> 1884 When building in the <filename>nativesdk-</filename>
1878 context, 1885 context,
1879 <link linkend='var-CXXFLAGS'><filename>CXXFLAGS</filename></link> 1886 <link linkend='var-CXXFLAGS'><filename>CXXFLAGS</filename></link>
1880 is set to the value of this variable by default. 1887 is set to the value of this variable by default.
@@ -2031,7 +2038,7 @@
2031 and then can be used as an override. 2038 and then can be used as an override.
2032 Here is an example where "python-native" is added to 2039 Here is an example where "python-native" is added to
2033 <link linkend='var-DEPENDS'><filename>DEPENDS</filename></link> 2040 <link linkend='var-DEPENDS'><filename>DEPENDS</filename></link>
2034 only when building for the native case: 2041 only when building for the <filename>-native</filename> case:
2035 <literallayout class='monospaced'> 2042 <literallayout class='monospaced'>
2036 DEPENDS_append_class-native = " python-native" 2043 DEPENDS_append_class-native = " python-native"
2037 </literallayout> 2044 </literallayout>
@@ -2567,7 +2574,7 @@
2567 <listitem><para> 2574 <listitem><para>
2568 <link linkend='var-BUILDSDK_CXXFLAGS'><filename>BUILDSDK_CXXFLAGS</filename></link> 2575 <link linkend='var-BUILDSDK_CXXFLAGS'><filename>BUILDSDK_CXXFLAGS</filename></link>
2569 when building for an SDK (i.e. 2576 when building for an SDK (i.e.
2570 <filename>nativesdk</filename>) 2577 <filename>nativesdk-</filename>)
2571 </para></listitem> 2578 </para></listitem>
2572 </itemizedlist> 2579 </itemizedlist>
2573 </para> 2580 </para>
@@ -4736,12 +4743,12 @@
4736 <listitem><para> 4743 <listitem><para>
4737 <filename>BUILD_CC_ARCH</filename> 4744 <filename>BUILD_CC_ARCH</filename>
4738 when building for the build host (i.e. 4745 when building for the build host (i.e.
4739 <filename>native</filename>) 4746 <filename>-native</filename>)
4740 </para></listitem> 4747 </para></listitem>
4741 <listitem><para> 4748 <listitem><para>
4742 <filename>BUILDSDK_CC_ARCH</filename> 4749 <filename>BUILDSDK_CC_ARCH</filename>
4743 when building for an SDK (i.e. 4750 when building for an SDK (i.e.
4744 <filename>nativesdk</filename>) 4751 <filename>nativesdk-</filename>)
4745 </para></listitem> 4752 </para></listitem>
4746 </itemizedlist> 4753 </itemizedlist>
4747 </para> 4754 </para>
@@ -11898,14 +11905,14 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
11898 <listitem><para>For recipes building for the target 11905 <listitem><para>For recipes building for the target
11899 machine, the value is "${STAGING_DIR}/${MACHINE}". 11906 machine, the value is "${STAGING_DIR}/${MACHINE}".
11900 </para></listitem> 11907 </para></listitem>
11901 <listitem><para>For <filename>native</filename> 11908 <listitem><para>For native recipes building
11902 recipes building
11903 for the build host, the value is empty given the 11909 for the build host, the value is empty given the
11904 assumption that when building for the build host, 11910 assumption that when building for the build host,
11905 the build host's own directories should be used. 11911 the build host's own directories should be used.
11906 </para></listitem> 11912 </para></listitem>
11907 <listitem><para>For <filename>nativesdk</filename> 11913 <listitem><para>For native SDK
11908 recipes that build for the SDK, the value is 11914 recipes that build for the SDK
11915 (<filename>nativesdk</filename>), the value is
11909 "${STAGING_DIR}/${MULTIMACH_HOST_SYS}". 11916 "${STAGING_DIR}/${MULTIMACH_HOST_SYS}".
11910 </para></listitem> 11917 </para></listitem>
11911 </itemizedlist> 11918 </itemizedlist>
@@ -12713,12 +12720,13 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
12713 "${<link linkend='var-TARGET_SYS'>TARGET_SYS</link>}-". 12720 "${<link linkend='var-TARGET_SYS'>TARGET_SYS</link>}-".
12714 </para></listitem> 12721 </para></listitem>
12715 <listitem><para> 12722 <listitem><para>
12716 For <filename>native</filename> recipes, the build 12723 For native recipes, the build system sets the
12717 system sets the variable to the value of 12724 variable to the value of
12718 <filename>BUILD_PREFIX</filename>. 12725 <filename>BUILD_PREFIX</filename>.
12719 </para></listitem> 12726 </para></listitem>
12720 <listitem><para> 12727 <listitem><para>
12721 For <filename>nativesdk</filename> recipes, the 12728 For native SDK recipes
12729 (<filename>nativesdk</filename>), the
12722 build system sets the variable to the value of 12730 build system sets the variable to the value of
12723 <filename>SDK_PREFIX</filename>. 12731 <filename>SDK_PREFIX</filename>.
12724 </para></listitem> 12732 </para></listitem>
@@ -12757,9 +12765,8 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
12757 Consider these two examples: 12765 Consider these two examples:
12758 <itemizedlist> 12766 <itemizedlist>
12759 <listitem><para> 12767 <listitem><para>
12760 Given a <filename>native</filename> recipe on a 12768 Given a native recipe on a 32-bit, x86 machine
12761 32-bit, x86 machine running Linux, the value is 12769 running Linux, the value is "i686-linux".
12762 "i686-linux".
12763 </para></listitem> 12770 </para></listitem>
12764 <listitem><para> 12771 <listitem><para>
12765 Given a recipe being built for a little-endian, 12772 Given a recipe being built for a little-endian,
@@ -13365,11 +13372,14 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
13365 toolchain set that runs on the 13372 toolchain set that runs on the
13366 <link linkend='var-SDKMACHINE'><filename>SDKMACHINE</filename></link>, 13373 <link linkend='var-SDKMACHINE'><filename>SDKMACHINE</filename></link>,
13367 and each package should usually have the prefix 13374 and each package should usually have the prefix
13368 "nativesdk-". 13375 <filename>nativesdk-</filename>.
13369 When building an SDK using 13376 For example, consider the following command when
13370 <filename>bitbake -c populate_sdk &lt;imagename&gt;</filename>, 13377 building an SDK:
13371 a default list of packages is set in this variable, but 13378 <literallayout class='monospaced'>
13372 you can add additional packages to the list. 13379 $ bitbake -c populate_sdk <replaceable>imagename</replaceable>
13380 </literallayout>
13381 In this case, a default list of packages is set in this
13382 variable, but you can add additional packages to the list.
13373 </para> 13383 </para>
13374 13384
13375 <para> 13385 <para>
diff --git a/documentation/ref-manual/technical-details.xml b/documentation/ref-manual/technical-details.xml
index 6b4deb3177..b4f6a832ed 100644
--- a/documentation/ref-manual/technical-details.xml
+++ b/documentation/ref-manual/technical-details.xml
@@ -470,17 +470,19 @@
470 </para> 470 </para>
471 471
472 <para> 472 <para>
473 To complicate the problem, there are things that should not be included in 473 To complicate the problem, there are things that should not be
474 the checksum. 474 included in the checksum.
475 First, there is the actual specific build path of a given task - 475 First, there is the actual specific build path of a given task -
476 the <link linkend='var-WORKDIR'><filename>WORKDIR</filename></link>. 476 the <link linkend='var-WORKDIR'><filename>WORKDIR</filename></link>.
477 It does not matter if the work directory changes because it should not 477 It does not matter if the work directory changes because it should
478 affect the output for target packages. 478 not affect the output for target packages.
479 Also, the build process has the objective of making native or cross packages relocatable. 479 Also, the build process has the objective of making native
480 The checksum therefore needs to exclude <filename>WORKDIR</filename>. 480 (build host) or cross packages (target hardware) relocatable.
481 The checksum therefore needs to exclude
482 <filename>WORKDIR</filename>.
481 The simplistic approach for excluding the work directory is to set 483 The simplistic approach for excluding the work directory is to set
482 <filename>WORKDIR</filename> to some fixed value and create the checksum 484 <filename>WORKDIR</filename> to some fixed value and create the
483 for the "run" script. 485 checksum for the "run" script.
484 </para> 486 </para>
485 487
486 <para> 488 <para>