summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <srifenbark@gmail.com>2015-09-23 09:34:28 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2015-10-21 23:06:22 +0100
commita87268ebbe4afa5dcaa4ca1b3ce668090fc3ff3b (patch)
treece0119a09cd9761464738f054120767c926281f6
parent1c7f462f915ce58e36fa452212323e8f25785435 (diff)
downloadpoky-a87268ebbe4afa5dcaa4ca1b3ce668090fc3ff3b.tar.gz
dev-manual: Updated the Marking Packages information.
Fixes [YOCTO #8375] Applied some suggested simpler wording for this bulleted item of information. Also, did some paragraph editing for better organization. (From yocto-docs rev: fd3e277b01ed6fd3580a1c008b1ac05bcfb98f38) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.xml21
1 files changed, 9 insertions, 12 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index a9922dfe31..ddf0ecd0c4 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -2708,23 +2708,20 @@
2708 is configured, it might be important to mark the 2708 is configured, it might be important to mark the
2709 packages produced as being specific to a particular 2709 packages produced as being specific to a particular
2710 machine, or to mark them as not being specific to 2710 machine, or to mark them as not being specific to
2711 a particular machine or architecture at all. 2711 a particular machine or architecture at all.</para>
2712 By default, packages produced for the target are 2712 <para>By default, packages apply to any machine with the
2713 marked as being specific to the architecture of the 2713 same architecture as the target machine.
2714 target machine because that is usually the desired 2714 When a recipe produces packages that are
2715 result. 2715 machine-specific (e.g. the
2716 However, if the recipe configures the software to be
2717 built specific to the target machine (e.g. the
2718 <ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink> 2716 <ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink>
2719 value is passed into the configure script or a patch 2717 value is passed into the configure script or a patch
2720 is applied only for a particular machine), then you 2718 is applied only for a particular machine), you should
2721 should mark the packages produced as being 2719 mark them as such by adding the following to the
2722 machine-specific by adding the following to the
2723 recipe: 2720 recipe:
2724 <literallayout class='monospaced'> 2721 <literallayout class='monospaced'>
2725 PACKAGE_ARCH = "${MACHINE_ARCH}" 2722 PACKAGE_ARCH = "${MACHINE_ARCH}"
2726 </literallayout> 2723 </literallayout></para>
2727 On the other hand, if the recipe produces packages 2724 <para>On the other hand, if the recipe produces packages
2728 that do not contain anything specific to the target 2725 that do not contain anything specific to the target
2729 machine or architecture at all (e.g. recipes 2726 machine or architecture at all (e.g. recipes
2730 that simply package script files or configuration 2727 that simply package script files or configuration