From e867967d606a9742008a94d16f81e365e6371ec3 Mon Sep 17 00:00:00 2001
From: Scott Rifenbark <scott.m.rifenbark@intel.com>
Date: Fri, 9 May 2014 14:19:48 +0300
Subject: ref-manual: Added links to new do_* sections.

With the creation of the new chapter that documents the 51
tasks defined by the OpenEmbedded build system, the remainder
of the ref-manual had many first-instance occurrences of do_*
task names that could be cross-referenced to the new sections.

I have added these links.

(From yocto-docs rev: 2ff39bd226a1d8f11924283bbaa3542a9d936ba3)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
 documentation/ref-manual/closer-look.xml | 47 ++++++++++++++++++++++++--------
 1 file changed, 35 insertions(+), 12 deletions(-)

(limited to 'documentation/ref-manual/closer-look.xml')

diff --git a/documentation/ref-manual/closer-look.xml b/documentation/ref-manual/closer-look.xml
index c223bbb0ce..7546215ae6 100644
--- a/documentation/ref-manual/closer-look.xml
+++ b/documentation/ref-manual/closer-look.xml
@@ -568,7 +568,9 @@
                 Another place the build system can get source files from is
                 through an SCM such as Git or Subversion.
                 In this case, a repository is cloned or checked out.
-                The <filename>do_fetch</filename> task inside BitBake uses
+                The
+                <link linkend='ref-tasks-fetch'><filename>do_fetch</filename></link>
+                task inside BitBake uses
                 the <link linkend='var-SRC_URI'><filename>SRC_URI</filename></link>
                 variable and the argument's prefix to determine the correct
                 fetcher module.
@@ -664,9 +666,16 @@
         </para>
 
         <para>
-            BitBake uses the <filename>do_package_write_*</filename> task to
+            BitBake uses the <filename>do_package_write_*</filename> tasks to
             place generated packages into the package holding area (e.g.
             <filename>do_package_write_ipk</filename> for IPK packages).
+            See the
+            "<link linkend='ref-tasks-package_write_deb'><filename>do_package_write_deb</filename></link>",
+            "<link linkend='ref-tasks-package_write_ipk'><filename>do_package_write_ipk</filename></link>",
+            "<link linkend='ref-tasks-package_write_rpm'><filename>do_package_write_rpm</filename></link>",
+            and
+            "<link linkend='ref-tasks-package_write_tar'><filename>do_package_write_tar</filename></link>"
+            sections for additional information.
         </para>
     </section>
 
@@ -700,8 +709,11 @@
             </para>
 
             <para>
-                The <filename>do_fetch</filename> and
-                <filename>do_unpack</filename> tasks fetch the source files
+                The
+                <link linkend='ref-tasks-fetch'><filename>do_fetch</filename></link>
+                and
+                <link linkend='ref-tasks-unpack'><filename>do_unpack</filename></link>
+                tasks fetch the source files
                 and unpack them into the work directory.
                 By default, everything is accomplished in the
                 <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>,
@@ -762,7 +774,9 @@
             </para>
 
             <para>
-                The <filename>do_patch</filename> task processes recipes by
+                The
+                <link linkend='ref-tasks-patch'><filename>do_patch</filename></link>
+                task processes recipes by
                 using the
                 <link linkend='var-SRC_URI'><filename>SRC_URI</filename></link>
                 variable to locate applicable patch files, which by default
@@ -810,7 +824,8 @@
                         </para>
 
                         <para>The configurations handled by the
-                        <filename>do_configure</filename> task are specific
+                        <link linkend='ref-tasks-configure'><filename>do_configure</filename></link>
+                        task are specific
                         to source code configuration for the source code
                         being built by the recipe.</para>
 
@@ -827,7 +842,8 @@
                     <listitem><para><emphasis><filename>do_compile</filename>:</emphasis>
                         Once a configuration task has been satisfied, BitBake
                         compiles the source using the
-                        <filename>do_compile</filename> task.
+                        <link linkend='ref-tasks-compile'><filename>do_compile</filename></link>
+                        task.
                         Compilation occurs in the directory pointed to by the
                         <link linkend='var-B'><filename>B</filename></link>
                         variable.
@@ -837,7 +853,8 @@
                         directory.</para></listitem>
                     <listitem><para><emphasis><filename>do_install</filename>:</emphasis>
                         Once compilation is done, BitBake executes the
-                        <filename>do_install</filename> task.
+                        <link linkend='ref-tasks-install'><filename>do_install</filename></link>
+                        task.
                         This task copies files from the <filename>B</filename>
                         directory and places them in a holding area pointed to
                         by the
@@ -858,8 +875,11 @@
             </para>
 
             <para>
-                The <filename>do_package</filename> and
-                <filename>do_packagedata</filename> tasks combine to analyze
+                The
+                <link linkend='ref-tasks-package'><filename>do_package</filename></link>
+                and
+                <link linkend='ref-tasks-packagedata'><filename>do_packagedata</filename></link>
+                tasks combine to analyze
                 the files found in the
                 <link linkend='var-D'><filename>D</filename></link> directory
                 and split them into subsets based on available packages and
@@ -935,7 +955,9 @@
             <para>
                 The image generation process consists of several stages and
                 depends on many variables.
-                The <filename>do_rootfs</filename> task uses these key variables
+                The
+                <link linkend='ref-tasks-rootfs'><filename>do_rootfs</filename></link>
+                task uses these key variables
                 to help create the list of packages to actually install:
                 <itemizedlist>
                     <listitem><para><link linkend='var-IMAGE_INSTALL'><filename>IMAGE_INSTALL</filename></link>:
@@ -1046,7 +1068,8 @@
                 section.
                 For information on advantages gained when building a
                 cross-development toolchain using the
-                <filename>do_populate_sdk</filename> task, see the
+                <link linkend='ref-tasks-populate_sdk'><filename>do_populate_sdk</filename></link>
+                task, see the
                 "<ulink url='&YOCTO_DOCS_ADT_URL;#optionally-building-a-toolchain-installer'>Optionally Building a Toolchain Installer</ulink>"
                 section in the Yocto Project Application Developer's Guide.
             </note>
-- 
cgit v1.2.3-54-g00ecf