From c92a266c8e452833f2a590721aa1c2bd6fbeb2e0 Mon Sep 17 00:00:00 2001 From: Jacob Kroon Date: Thu, 28 May 2020 08:41:15 +0200 Subject: doc: More explanation to tasks that recursively depend on themselves Signed-off-by: Jacob Kroon Signed-off-by: Richard Purdie --- doc/bitbake-user-manual/bitbake-user-manual-metadata.xml | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) (limited to 'doc') diff --git a/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml b/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml index 95a8b95b1..069a0ec80 100644 --- a/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml +++ b/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml @@ -2565,15 +2565,17 @@ - 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: do_a[recrdeptask] = "do_a do_b" + In the same way as before, this means that the do_a + and do_b tasks of the current recipe and all + recipes reachable (by way of dependencies) from the recipe + must run before the do_a task can run. In this + case BitBake will ignore the current recipe's do_a + task circular dependency on itself. -- cgit 1.2.3-korg