From 28bb8ef7f737034055f3485795179cfdcdb9a41f Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Fri, 12 Aug 2016 09:17:02 -0700 Subject: bitbake-user-manual: Re-write "Dependencies Internal to the .bb File" Fixes [YOCTO #10117] Applied a re-write to better clarify the behavior of dependencies. Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- .../bitbake-user-manual-metadata.xml | 54 ++++++++++++---------- 1 file changed, 29 insertions(+), 25 deletions(-) (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 3d9234cba..5df00050c 100644 --- a/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml +++ b/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml @@ -1848,44 +1848,48 @@ addtask printdate after do_fetch before do_build - In this example, the printdate task is - depends on the completion of the do_fetch + In this example, the do_printdate + task depends on the completion of the + do_fetch task, and the + do_build task depends on the + completion of the do_printdate 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: + + For a task to run, it must be a direct or indirect + dependency of some other task that is scheduled to + run. + + 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. + addtask mytask before do_configure + causes do_mytask to run before + do_configure runs. + Be aware that do_mytask still only + runs if its input checksum + has changed since the last time it was run. + Changes to the input checksum of + do_mytask also indirectly cause + do_configure to run. 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: + by itself never causes do_mytask + to run. + do_mytask can still be run manually + as follows: $ bitbake recipe -c mytask - mytask could also be declared as - a dependency of some other task. - Regardless, the task is run after + Declaring do_mytask as a dependency + of some other task that is scheduled to run also causes + it to run. + Regardless, the task runs after do_configure. - + -- cgit 1.2.3-korg