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

sdk-manual: Edits to "Dependency Detection and Mapping"

Browse Source 
Updated various prose for better understanding.

(From yocto-docs rev: ddbd66d7732bbc8b4940c660f8a8c941a5cc4ea2)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2018-05-31 09:58:18 -07:00
committed by Richard Purdie
parent 5a9e1870db
commit 290809334a
1 changed files with 13 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/sdk-manual/sdk-extensible.xml
+13 -12
View File
@@ -1114,26 +1114,27 @@
detect build-time dependencies and map them to other recipes detect build-time dependencies and map them to other recipes
in the system. in the system.
During this mapping, the command fills in the names of those During this mapping, the command fills in the names of those
recipes in the recipes as part of the
<ulink url='&YOCTO_DOCS_REF_URL;#var-DEPENDS'><filename>DEPENDS</filename></ulink> <ulink url='&YOCTO_DOCS_REF_URL;#var-DEPENDS'><filename>DEPENDS</filename></ulink>
value within the recipe. variable within the recipe.
If a dependency cannot be mapped, then a comment is placed in If a dependency cannot be mapped, <filename>devtool</filename>
the recipe indicating such. places a comment in the recipe indicating such.
The inability to map a dependency might be caused because the The inability to map a dependency can result from naming not
naming is not recognized or because the dependency simply is being recognized or because the dependency simply is not
not available. available.
For cases where the dependency is not available, you must use For cases where the dependency is not available, you must use
the <filename>devtool add</filename> command to add an the <filename>devtool add</filename> command to add an
additional recipe to satisfy the dependency and then come additional recipe that satisfies the dependency.
back to the first recipe and add its name to Once you add that recipe, you need to update the
<filename>DEPENDS</filename>. <filename>DEPENDS</filename> variable in the original recipe
to include the new recipe.
</para> </para>
<para> <para>
If you need to add runtime dependencies, you can do so by If you need to add runtime dependencies, you can do so by
adding the following to your recipe: adding the following to your recipe:
<literallayout class='monospaced'> <literallayout class='monospaced'>
RDEPENDS_${PN} += "dependency1 dependency2 ..." RDEPENDS_${PN} += "<replaceable>dependency1 dependency2 ...</replaceable>"
</literallayout> </literallayout>
<note> <note>
The <filename>devtool add</filename> command often cannot The <filename>devtool add</filename> command often cannot
@@ -1144,7 +1145,7 @@
script for the software the recipe is building for further script for the software the recipe is building for further
details. details.
In some cases, you might find you can substitute the In some cases, you might find you can substitute the
dependency for an option to disable the associated dependency with an option that disables the associated
functionality passed to the configure script. functionality passed to the configure script.
</note> </note>
</para> </para>