From ada90f68afd17cb85cb5957f3f91b537ee3599f6 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Thu, 14 Jul 2016 12:00:09 -0700 Subject: bitbake-user-manual: Added review changes to recursive section. Applied formatting to a "after" word that should be after. Also added a new clarifying paragraph in the "Recursive Dependencies" section. Fixes [YOCTO #9861] Signed-off-by: Scott Rifenbark --- doc/bitbake-user-manual/bitbake-user-manual-metadata.xml | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) (limited to 'doc/bitbake-user-manual/bitbake-user-manual-metadata.xml') diff --git a/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml b/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml index 857f8b279..4cc647fe4 100644 --- a/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml +++ b/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml @@ -1686,7 +1686,7 @@ recipe is built. In this example, mytask is run at an unspecified time relative to other tasks within - the recipe, since "after" is not used. + the recipe, since after is not used. The directive @@ -1772,6 +1772,19 @@ and added. + + The "recrdeptask" flag is most commonly used in high-level + recipes that need to wait for some task to finish "globally". + For example, image.bbclass has the following: + + do_rootfs[recrdeptask] += "do_packagedata" + + This statement says that the do_packagedata + task of all recipes reachable (by way of dependencies) from the + image recipe must run before the do_rootfs + task can run. + + You might want to not only have BitBake look for dependencies of those tasks, but also have BitBake look -- cgit 1.2.3-korg