diff options
| author |   Scott Rifenbark <scott.m.rifenbark@intel.com> | 2014-05-09 14:19:48 +0300 |
|---|---|---|
| committer |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2014-05-13 07:50:58 +0100 |
| commit | e867967d606a9742008a94d16f81e365e6371ec3 (patch) | |
| tree | b433593b9b310e7203dd6ededd735f7c40bf916c /documentation/ref-manual/usingpoky.xml | |
| parent | 2f4d0722ce42e6381228b335d2bbd5a5901bb594 (diff) | |
| download | openembedded-core-contrib-e867967d606a9742008a94d16f81e365e6371ec3.tar.gz | |
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>
Diffstat (limited to 'documentation/ref-manual/usingpoky.xml')
| -rw-r--r-- | documentation/ref-manual/usingpoky.xml | 14 |
1 files changed, 9 insertions, 5 deletions
diff --git a/documentation/ref-manual/usingpoky.xml b/documentation/ref-manual/usingpoky.xml index a8a6f3b92a..3748ac21bb 100644 --- a/documentation/ref-manual/usingpoky.xml +++ b/documentation/ref-manual/usingpoky.xml @@ -280,9 +280,10 @@ <listitem><para><emphasis><filename>eglibc-initial</filename> fails to build</emphasis>: If your development host system has the unpatched <filename>GNU Make 3.82</filename>, - the <filename>do_install</filename> task - fails for <filename>eglibc-initial</filename> during the - build.</para> + the + <link linkend='ref-tasks-install'><filename>do_install</filename></link> + task fails for <filename>eglibc-initial</filename> during + the build.</para> <para>Typically, every distribution that ships <filename>GNU Make 3.82</filename> as the default already has the patched version. @@ -370,8 +371,11 @@ <para> Following is an example written in Python. - The code handles logging for a function that determines the number of tasks - needed to be run: + The code handles logging for a function that determines the + number of tasks needed to be run. + See the + "<link linkend='ref-tasks-listtasks'><filename>do_listtasks</filename></link>" + section for additional information: <literallayout class='monospaced'> python do_listtasks() { bb.debug(2, "Starting to figure out the task list") |