path: root/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
diff options
authorScott Rifenbark <srifenbark@gmail.com>2016-07-11 14:24:22 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-07-21 07:47:35 +0100
commit231deeb2b0b3847cba971ca30c16e29357100ae6 (patch)
tree803637571dfc55305218b978e4561d3990203243 /doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
parent886afd6d876c9ae04cf681931db8f1774dc53096 (diff)
bitbake-user-manual: Updated dependency section for tasks
Fixes [YOCTO #9861] I updated the section on dependencies to give a couple of examples for task dependencies within a single recipe and dependencies for tasks between two individual recipes. Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Diffstat (limited to 'doc/bitbake-user-manual/bitbake-user-manual-metadata.xml')
1 files changed, 26 insertions, 9 deletions
diff --git a/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml b/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
index 26fe58f8..646f6744 100644
--- a/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
+++ b/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
@@ -1624,15 +1624,32 @@
- To allow for efficient operation given multiple processes
- executing in parallel, BitBake handles dependencies at
- the task level.
- BitBake supports a robust method to handle these dependencies.
- </para>
- <para>
- This section describes several types of dependency mechanisms.
- </para>
+ To allow for efficient parallel processing, BitBake handles
+ dependencies at the task level.
+ Dependencies can exist both between tasks within a single recipe
+ and between tasks in different recipes.
+ Following are examples of each:
+ <itemizedlist>
+ <listitem><para>For tasks within a single recipe, a
+ recipe's <filename>do_configure</filename>
+ task might need to complete before its
+ <filename>do_compile</filename> task can run.
+ </para></listitem>
+ <listitem><para>For tasks in different recipes, one
+ recipe's <filename>do_configure</filename>
+ task might require another recipe's
+ <filename>do_populate_sysroot</filename>
+ task to finish first such that the libraries and headers
+ provided by the other recipe are available.
+ </para></listitem>
+ </itemizedlist>
+ </para>
+ <para>
+ This section describes several ways to declare dependencies.
+ Remember, even though dependencies are declared in different ways, they
+ are all simply dependencies between tasks.
+ </para>
<section id='dependencies-internal-to-the-bb-file'>
<title>Dependencies Internal to the <filename>.bb</filename> File</title>