diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2012-09-04 12:05:21 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2012-09-14 09:50:45 +0100 |
commit | 64b9137b43207c0505c4d8c26e654152b5a699da (patch) | |
tree | 3620f581aa55f119e3e2d2c48592cd8e9d307b73 /documentation/dev-manual/dev-manual-start.xml | |
parent | 3fa4a6a146666d6817de1076aa0a92198167fb88 (diff) | |
download | poky-64b9137b43207c0505c4d8c26e654152b5a699da.tar.gz |
documentation: Fixed links to BitBake User Manual
Robert P. J. Day pointed out a link in the development manual that
was for the BitBake User Manual. The link resolved to an old,
non-maintained version of BitBake documentation. According to
Richard Purdie, the BitBake docs referenced should be the ones
that ship in the bitbake/doc/manual directory of poky. The
YP docs had been using a variable named BITBAKE_DOCS_URL that
also resolved to the antiquated user manual site. Consequently,
there were many links that needed fixed across both the YP
Development Manual and the YP Reference Manual. Each of these
references now points in general to the bitbake/doc/manual
directory in poky for more information.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 12f77236b602e9ec43e845c8cec060ad342af19c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/dev-manual/dev-manual-start.xml')
-rw-r--r-- | documentation/dev-manual/dev-manual-start.xml | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/documentation/dev-manual/dev-manual-start.xml b/documentation/dev-manual/dev-manual-start.xml index 0d211807bc..3209cb29b7 100644 --- a/documentation/dev-manual/dev-manual-start.xml +++ b/documentation/dev-manual/dev-manual-start.xml | |||
@@ -32,7 +32,7 @@ | |||
32 | 32 | ||
33 | <para> | 33 | <para> |
34 | You can use the OpenEmbedded build system, which uses | 34 | You can use the OpenEmbedded build system, which uses |
35 | <ulink url='&BITBAKE_DOCS_URL;'>BitBake</ulink>, to develop complete Linux | 35 | BitBake to develop complete Linux |
36 | images and associated user-space applications for architectures based on ARM, MIPS, PowerPC, | 36 | images and associated user-space applications for architectures based on ARM, MIPS, PowerPC, |
37 | x86 and x86-64. | 37 | x86 and x86-64. |
38 | While the Yocto Project does not provide a strict testing framework, | 38 | While the Yocto Project does not provide a strict testing framework, |
@@ -277,8 +277,9 @@ | |||
277 | a centralized tarball download directory through the | 277 | a centralized tarball download directory through the |
278 | <filename><ulink url='&YOCTO_DOCS_REF_URL;#var-DL_DIR'>DL_DIR</ulink></filename> variable.</para></listitem> | 278 | <filename><ulink url='&YOCTO_DOCS_REF_URL;#var-DL_DIR'>DL_DIR</ulink></filename> variable.</para></listitem> |
279 | <listitem><para>Build the image using the <filename>bitbake</filename> command. | 279 | <listitem><para>Build the image using the <filename>bitbake</filename> command. |
280 | If you want information on BitBake, see the user manual at | 280 | If you want information on BitBake, see the user manual inculded in the |
281 | <ulink url='&OE_DOCS_URL;/bitbake/html'></ulink>.</para></listitem> | 281 | <filename>bitbake/doc/manual</filename> directory of the |
282 | <link linkend='source-directory'>Source Directory</link>.</para></listitem> | ||
282 | <listitem><para>Run the image either on the actual hardware or using the QEMU | 283 | <listitem><para>Run the image either on the actual hardware or using the QEMU |
283 | emulator.</para></listitem> | 284 | emulator.</para></listitem> |
284 | </orderedlist> | 285 | </orderedlist> |