summaryrefslogtreecommitdiffstats
path: root/documentation/sdk-manual/sdk-extensible.xml
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/sdk-manual/sdk-extensible.xml')
-rw-r--r--documentation/sdk-manual/sdk-extensible.xml25
1 files changed, 13 insertions, 12 deletions
diff --git a/documentation/sdk-manual/sdk-extensible.xml b/documentation/sdk-manual/sdk-extensible.xml
index 01dd76f1da..2c4b5b99d7 100644
--- a/documentation/sdk-manual/sdk-extensible.xml
+++ b/documentation/sdk-manual/sdk-extensible.xml
@@ -1114,26 +1114,27 @@
1114 detect build-time dependencies and map them to other recipes 1114 detect build-time dependencies and map them to other recipes
1115 in the system. 1115 in the system.
1116 During this mapping, the command fills in the names of those 1116 During this mapping, the command fills in the names of those
1117 recipes in the 1117 recipes as part of the
1118 <ulink url='&YOCTO_DOCS_REF_URL;#var-DEPENDS'><filename>DEPENDS</filename></ulink> 1118 <ulink url='&YOCTO_DOCS_REF_URL;#var-DEPENDS'><filename>DEPENDS</filename></ulink>
1119 value within the recipe. 1119 variable within the recipe.
1120 If a dependency cannot be mapped, then a comment is placed in 1120 If a dependency cannot be mapped, <filename>devtool</filename>
1121 the recipe indicating such. 1121 places a comment in the recipe indicating such.
1122 The inability to map a dependency might be caused because the 1122 The inability to map a dependency can result from naming not
1123 naming is not recognized or because the dependency simply is 1123 being recognized or because the dependency simply is not
1124 not available. 1124 available.
1125 For cases where the dependency is not available, you must use 1125 For cases where the dependency is not available, you must use
1126 the <filename>devtool add</filename> command to add an 1126 the <filename>devtool add</filename> command to add an
1127 additional recipe to satisfy the dependency and then come 1127 additional recipe that satisfies the dependency.
1128 back to the first recipe and add its name to 1128 Once you add that recipe, you need to update the
1129 <filename>DEPENDS</filename>. 1129 <filename>DEPENDS</filename> variable in the original recipe
1130 to include the new recipe.
1130 </para> 1131 </para>
1131 1132
1132 <para> 1133 <para>
1133 If you need to add runtime dependencies, you can do so by 1134 If you need to add runtime dependencies, you can do so by
1134 adding the following to your recipe: 1135 adding the following to your recipe:
1135 <literallayout class='monospaced'> 1136 <literallayout class='monospaced'>
1136 RDEPENDS_${PN} += "dependency1 dependency2 ..." 1137 RDEPENDS_${PN} += "<replaceable>dependency1 dependency2 ...</replaceable>"
1137 </literallayout> 1138 </literallayout>
1138 <note> 1139 <note>
1139 The <filename>devtool add</filename> command often cannot 1140 The <filename>devtool add</filename> command often cannot
@@ -1144,7 +1145,7 @@
1144 script for the software the recipe is building for further 1145 script for the software the recipe is building for further
1145 details. 1146 details.
1146 In some cases, you might find you can substitute the 1147 In some cases, you might find you can substitute the
1147 dependency for an option to disable the associated 1148 dependency with an option that disables the associated
1148 functionality passed to the configure script. 1149 functionality passed to the configure script.
1149 </note> 1150 </note>
1150 </para> 1151 </para>