summaryrefslogtreecommitdiffstats
path: root/bitbake
diff options
context:
space:
mode:
authorJacob Kroon <jacob.kroon@gmail.com>2020-05-28 08:41:15 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2020-06-05 21:37:15 +0100
commit6af527ca94e4fb89c83baebd8885fb30b8ad5598 (patch)
treef57c9d29872d835e9d092e0ae336eeabe9b26e68 /bitbake
parent81833e0ee838bd3e93e84578f2828b559d94d399 (diff)
downloadpoky-6af527ca94e4fb89c83baebd8885fb30b8ad5598.tar.gz
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>
Diffstat (limited to 'bitbake')
-rw-r--r--bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml14
1 files changed, 8 insertions, 6 deletions
diff --git a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
index 95a8b95b17..069a0ec809 100644
--- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
+++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
@@ -2565,15 +2565,17 @@
2565 </para> 2565 </para>
2566 2566
2567 <para> 2567 <para>
2568 You might want to not only have BitBake look for 2568 BitBake allows a task to recursively depend on itself by
2569 dependencies of those tasks, but also have BitBake look 2569 referencing itself in the task list:
2570 for build-time and runtime dependencies of the dependent
2571 tasks as well.
2572 If that is the case, you need to reference the task name
2573 itself in the task list:
2574 <literallayout class='monospaced'> 2570 <literallayout class='monospaced'>
2575 do_a[recrdeptask] = "do_a do_b" 2571 do_a[recrdeptask] = "do_a do_b"
2576 </literallayout> 2572 </literallayout>
2573 In the same way as before, this means that the <filename>do_a</filename>
2574 and <filename>do_b</filename> tasks of the current recipe and all
2575 recipes reachable (by way of dependencies) from the recipe
2576 must run before the <filename>do_a</filename> task can run. In this
2577 case BitBake will ignore the current recipe's <filename>do_a</filename>
2578 task circular dependency on itself.
2577 </para> 2579 </para>
2578 </section> 2580 </section>
2579 2581