bitbake: 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] (Bitbake rev: ada90f68afd17cb85cb5957f3f91b537ee3599f6) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
35081f5518
commit
4bc1ee5de4
|
@ -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.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
The directive
|
||||
|
@ -1772,6 +1772,19 @@
|
|||
and added.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
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
|
||||
|
|
Loading…
Reference in New Issue