mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-05-30 00:20:08 +00:00
Code Issues Projects Releases Wiki Activity

dev-manual: Updated the Marking Packages information.

Browse Source 
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>
This commit is contained in:
Scott Rifenbark
2015-09-23 09:34:28 -07:00
committed by Richard Purdie
parent 1c7f462f91
commit a87268ebbe
1 changed files with 9 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/dev-manual/dev-manual-common-tasks.xml
+9 -12
View File
@@ -2708,23 +2708,20 @@
is configured, it might be important to mark the is configured, it might be important to mark the
packages produced as being specific to a particular packages produced as being specific to a particular
machine, or to mark them as not being specific to machine, or to mark them as not being specific to
a particular machine or architecture at all. a particular machine or architecture at all.</para>
By default, packages produced for the target are <para>By default, packages apply to any machine with the
marked as being specific to the architecture of the same architecture as the target machine.
target machine because that is usually the desired When a recipe produces packages that are
result. machine-specific (e.g. the
However, if the recipe configures the software to be
built specific to the target machine (e.g. the
<ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink> <ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink>
value is passed into the configure script or a patch value is passed into the configure script or a patch
is applied only for a particular machine), then you is applied only for a particular machine), you should
should mark the packages produced as being mark them as such by adding the following to the
machine-specific by adding the following to the
recipe: recipe:
<literallayout class='monospaced'> <literallayout class='monospaced'>
PACKAGE_ARCH = "${MACHINE_ARCH}" PACKAGE_ARCH = "${MACHINE_ARCH}"
</literallayout> </literallayout></para>
On the other hand, if the recipe produces packages <para>On the other hand, if the recipe produces packages
that do not contain anything specific to the target that do not contain anything specific to the target
machine or architecture at all (e.g. recipes machine or architecture at all (e.g. recipes
that simply package script files or configuration that simply package script files or configuration