path: root/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
diff options
authorScott Rifenbark <srifenbark@gmail.com>2016-07-14 12:00:09 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-07-21 07:47:35 +0100
commitada90f68afd17cb85cb5957f3f91b537ee3599f6 (patch)
treecadc1d3fab2b97b808ebafa57237f876dcae1699 /doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
parent47e03b1789ee1c18407dbac33a6c235752019865 (diff)
bitbake-user-manual: Added review changes to recursive section.
Applied formatting to a "after" word that should be <filename>after</filename>. Also added a new clarifying paragraph in the "Recursive Dependencies" section. Fixes [YOCTO #9861] Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Diffstat (limited to 'doc/bitbake-user-manual/bitbake-user-manual-metadata.xml')
1 files changed, 14 insertions, 1 deletions
diff --git a/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml b/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
index 857f8b27..4cc647fe 100644
--- a/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
+++ b/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
@@ -1686,7 +1686,7 @@
recipe is built.
In this example, <filename>mytask</filename> is run
at an unspecified time relative to other tasks within
- the recipe, since "after" is not used.
+ the recipe, since <filename>after</filename> is not used.
The directive
@@ -1773,6 +1773,19 @@
+ The "recrdeptask" flag is most commonly used in high-level
+ recipes that need to wait for some task to finish "globally".
+ For example, <filename>image.bbclass</filename> has the following:
+ <literallayout class='monospaced'>
+ do_rootfs[recrdeptask] += "do_packagedata"
+ </literallayout>
+ This statement says that the <filename>do_packagedata</filename>
+ task of all recipes reachable (by way of dependencies) from the
+ image recipe must run before the <filename>do_rootfs</filename>
+ task can run.
+ </para>
+ <para>
You might want to not only have BitBake look for
dependencies of those tasks, but also have BitBake look
for build-time and runtime dependencies of the dependent