bitbake: doc: More explanation to tasks that recursively depend on themselves

(Bitbake rev: f92e19a3b3d89eb26eeb74b18ca01248767035b5)

Signed-off-by: Jacob Kroon <jacob.kroon@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit c92a266c8e452833f2a590721aa1c2bd6fbeb2e0)
Signed-off-by: Steve Sakoman <steve@sakoman.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Jacob Kroon
2020-05-28 08:41:15 +02:00
committed by Richard Purdie
parent 81833e0ee8
commit 6af527ca94

View File

@@ -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>