|
@@ -2565,15 +2565,17 @@
|
|
|
</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
|
|
|
- tasks as well.
|
|
|
- If that is the case, you need to reference the task name
|
|
|
- itself in the task list:
|
|
|
+ BitBake allows a task to recursively depend on itself by
|
|
|
+ referencing itself in the task list:
|
|
|
<literallayout class='monospaced'>
|
|
|
do_a[recrdeptask] = "do_a do_b"
|
|
|
</literallayout>
|
|
|
+ In the same way as before, this means that the <filename>do_a</filename>
|
|
|
+ and <filename>do_b</filename> tasks of the current recipe and all
|
|
|
+ recipes reachable (by way of dependencies) from the recipe
|
|
|
+ must run before the <filename>do_a</filename> task can run. In this
|
|
|
+ case BitBake will ignore the current recipe's <filename>do_a</filename>
|
|
|
+ task circular dependency on itself.
|
|
|
</para>
|
|
|
</section>
|
|
|
|