aboutsummaryrefslogtreecommitdiffstats
path: root/documentation/dev-manual/dev-manual-common-tasks.xml
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 /documentation/dev-manual/dev-manual-common-tasks.xml
parent1c7f462f915ce58e36fa452212323e8f25785435 (diff)
downloadopenembedded-core-contrib-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>
Diffstat (limited to 'documentation/dev-manual/dev-manual-common-tasks.xml')
-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 @@
is configured, it might be important to mark the
packages produced as being specific to a particular
machine, or to mark them as not being specific to
- a particular machine or architecture at all.
- By default, packages produced for the target are
- marked as being specific to the architecture of the
- target machine because that is usually the desired
- result.
- However, if the recipe configures the software to be
- built specific to the target machine (e.g. the
+ a particular machine or architecture at all.</para>
+ <para>By default, packages apply to any machine with the
+ same architecture as the target machine.
+ When a recipe produces packages that are
+ machine-specific (e.g. the
<ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink>
value is passed into the configure script or a patch
- is applied only for a particular machine), then you
- should mark the packages produced as being
- machine-specific by adding the following to the
+ is applied only for a particular machine), you should
+ mark them as such by adding the following to the
recipe:
<literallayout class='monospaced'>
PACKAGE_ARCH = "${MACHINE_ARCH}"
- </literallayout>
- On the other hand, if the recipe produces packages
+ </literallayout></para>
+ <para>On the other hand, if the recipe produces packages
that do not contain anything specific to the target
machine or architecture at all (e.g. recipes
that simply package script files or configuration