From 8c55a9cf882eb7edd1ebfbcdfc66a330b401926a Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Tue, 12 Jul 2016 13:41:12 -0700 Subject: bitbake: bitbake-user-manual: Added a note providing examples of task dependencies Fixes [YOCTO #9861] In the "Dependencies internal to the .bb File" section, I placed a note providing more detail on how recipes are built regarding task dependency. (Bitbake rev: c2e72928fbd21d622860a54a55f4239ba27c07a2) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- .../bitbake-user-manual-metadata.xml | 34 ++++++++++++++++++++++ 1 file changed, 34 insertions(+) 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 646f6744e6..857f8b279c 100644 --- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml +++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml @@ -1670,6 +1670,40 @@ task. And, the do_build depends on the completion of the printdate task. + + Recipes are built by having their + do_build (not to be confused with + do_compile) tasks executed. + For a task to run when a recipe is built, the task must + therefore be a direct or indirect dependency of + do_build. + For illustration, here are some examples: + + + The directive + addtask mytask before do_build + causes mytask to run when the + 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 directive + addtask mytask after do_configure + by itself does not cause mytask + to run when the recipe is built. + The task can still be run manually using the following: + + $ bitbake recipe -c mytask + + mytask could also be declared as + a dependency of some other task. + Regardless, the task is run after + do_configure. + + + -- cgit 1.2.3-korg