ref-manual: Fixed internal links and links to dev-manual

Dev-manual title has changed to the Yocto Project Development Tasks
Manual.  I fixed these links.  Also, had to fix a couple links
that were in an external <ulink> style whereas they should have
been in an internal style (<link>).

(From yocto-docs rev: da5317f802975eaf6b2c5d4026892e5f2051760a)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2017-10-16 13:38:21 -07:00 committed by Richard Purdie
parent a6db326292
commit b8e6656319

View File

@ -36,9 +36,10 @@
</para>
<para>
The first thing BitBake does is look for the <filename>bitbake.conf</filename> file.
The first thing BitBake does is look for the
<filename>bitbake.conf</filename> file.
This file resides in the
<ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>
<link linkend='source-directory'>Source Directory</link>
within the <filename>meta/conf/</filename> directory.
BitBake finds it by examining its
<link linkend='var-BBPATH'><filename>BBPATH</filename></link> environment
@ -92,8 +93,8 @@
<filename>meta/recipes-*/</filename> directory within Poky.
Adding extra content to <filename>BBFILES</filename> is best achieved through the use of
BitBake layers as described in the
"<ulink url='&YOCTO_DOCS_DEV_URL;#understanding-and-creating-layers'>Understanding and
Creating Layers</ulink>" section of the Yocto Project Development Manual.
"<ulink url='&YOCTO_DOCS_DEV_URL;#understanding-and-creating-layers'>Understanding and Creating Layers</ulink>"
section of the Yocto Project Development Tasks Manual.
</para>
<para>
@ -227,13 +228,14 @@
<para>
Dependencies are defined through several variables.
You can find information about variables BitBake uses in the BitBake documentation,
which is found in the <filename>bitbake/doc/manual</filename> directory within the
<ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
You can find information about variables BitBake uses in the
BitBake documentation, which is found in the
<filename>bitbake/doc/manual</filename> directory within the
<link linkend='source-directory'>Source Directory</link>.
At a basic level, it is sufficient to know that BitBake uses the
<filename><link linkend='var-DEPENDS'>DEPENDS</link></filename> and
<filename><link linkend='var-RDEPENDS'>RDEPENDS</link></filename> variables when
calculating dependencies.
<filename><link linkend='var-RDEPENDS'>RDEPENDS</link></filename>
variables when calculating dependencies.
</para>
</section>
@ -448,20 +450,23 @@ Options:
You can find information about the options and formats of entries for specific
fetchers in the BitBake manual located in the
<filename>bitbake/doc/manual</filename> directory of the
<ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
<link linkend='source-directory'>Source Directory</link>.
</para>
<para>
One useful feature for certain Source Code Manager (SCM) fetchers is the ability to
"auto-update" when the upstream SCM changes version.
Since this ability requires certain functionality from the SCM, not all
systems support it.
Currently Subversion, Bazaar and to a limited extent, Git support the ability to "auto-update".
One useful feature for certain Source Code Manager (SCM) fetchers
is the ability to "auto-update" when the upstream SCM changes
version.
Since this ability requires certain functionality from the SCM,
not all systems support it.
Currently Subversion, Bazaar and to a limited extent, Git support
the ability to "auto-update".
This feature works using the <filename><link linkend='var-SRCREV'>SRCREV</link></filename>
variable.
See the
"<ulink url='&YOCTO_DOCS_DEV_URL;#platdev-appdev-srcrev'>Using an External SCM</ulink>" section
in the Yocto Project Development Manual for more information.
"<ulink url='&YOCTO_DOCS_DEV_URL;#platdev-appdev-srcrev'>Using an External SCM</ulink>"
section in the Yocto Project Development Tasks Manual for more
information.
</para>
</section>