documentation/poky-ref-manual: Various minor link and formatting changes

This is the second pass through the manual after applying initial
poky.ent variables and various fixes.  These changes here were found
and made during a QA of the made manual.

(From yocto-docs rev: a1551b5233a33f5fec6815c64e784212a7d02c4b)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2012-06-14 07:38:09 -07:00
committed by Richard Purdie
parent fcf7db01c0
commit 953ad50a27
3 changed files with 20 additions and 22 deletions

View File

@@ -83,7 +83,7 @@
The current release of the Yocto Project no longer supports the Anjuta plug-in.
However, the Poky Anjuta Plug-in is available to download directly from the Poky
Git repository located through the web interface at
<ulink url="http://git.yoctoproject.org/"></ulink> under IDE Plugins.
<ulink url="&YOCTO_GIT_URL;"></ulink> under IDE Plugins.
The community is free to continue supporting it beyond the Yocto Project 0.9
Release.
</note>
@@ -92,10 +92,8 @@
with other plug-ins installed into the Eclipse IDE.
Once you have your environment setup you need to configure the Eclipse plug-in.
For information on how to install and configure the Eclipse plug-in, see the
<ulink url='http://www.yoctoproject.org/docs/1.1.1/adt-manual/adt-manual.html#adt-eclipse'>
"Working Within Eclipse"</ulink> chapter in the
<ulink url='http://www.yoctoproject.org/docs/1.1.1/adt-manual/adt-manual.html'>
"Application Development Toolkit (ADT) User's Guide."</ulink>
"<ulink url='&YOCTO_DOCS_ADT_URL;#adt-eclipse'>Working Within Eclipse</ulink>" chapter in the
Yocto Project Application Development Toolkit (ADT) User's Guide.
</para>
</section>
@@ -103,8 +101,8 @@
<title>External Development Using the QEMU Emulator</title>
<para>
Running Poky QEMU images is covered in the
<ulink url="http://www.yoctoproject.org/docs/1.1.1/yocto-project-qs/yocto-project-qs.html">
Yocto Project Quick Start</ulink> in the "A Quick Test Run" section.
"<ulink url='&YOCTO_DOCS_ADT_URL;#test-run'>A Quick Test Run</ulink>" section of
the Yocto Project Quick Start.
</para>
<para>
The QEMU images shipped with the Yocto Project contain complete toolchains
@@ -163,8 +161,8 @@
<para>
Working directly with the Yocto Project is a fast and effective development technique.
The idea is that you can directly edit files in a working directory
(<glossterm><link linkend='var-WORKDIR'>WORKDIR</link></glossterm>)
or the source directory (<glossterm><link linkend='var-S'>S</link></glossterm>)
(<filename><link linkend='var-WORKDIR'>WORKDIR</link></filename>)
or the source directory (<filename><link linkend='var-S'>S</link></filename>)
and then force specific tasks to rerun in order to test the changes.
An example session working on the matchbox-desktop package might
look like this:
@@ -204,16 +202,16 @@
<para>
It is useful when making changes directly to the work directory files to do
so using the Quilt tool as detailed in the
<link linkend='usingpoky-modifying-packages-quilt'>
Modifying Package Source Code with Quilt</link> section.
"<link linkend='usingpoky-modifying-packages-quilt'>Modifying Package Source Code with Quilt</link>"
section.
Using Quilt, you can copy patches into the recipe directory and use the patches directly
through use of the <glossterm><link linkend='var-SRC_URI'>SRC_URI</link></glossterm> variable.
through use of the <filename><link linkend='var-SRC_URI'>SRC_URI</link></filename> variable.
</para>
<para>
For a review of the skills used in this section, see the
<link linkend="usingpoky-components-bitbake">BitBake</link> and
<link linkend="usingpoky-debugging-taskrunning">Running Specific Tasks</link> sections
"<link linkend="usingpoky-components-bitbake">BitBake</link>" and
"<link linkend="usingpoky-debugging-taskrunning">Running Specific Tasks</link>" sections
in this manual.
</para>
</section>
@@ -273,8 +271,8 @@
<para>
The default shell used by <filename>devshell</filename> is xterm.
You can use other terminal forms by setting the
<glossterm><link linkend='var-TERMCMD'>TERMCMD</link></glossterm> and
<glossterm><link linkend='var-TERMCMDRUN'>TERMCMDRUN</link></glossterm> variables
<filename><link linkend='var-TERMCMD'>TERMCMD</link></filename> and
<filename><link linkend='var-TERMCMDRUN'>TERMCMDRUN</link></filename> variables
in the Yocto Project's <filename>local.conf</filename> file found in the build
directory.
For examples of the other options available, see the "UI/Interaction Configuration"

View File

@@ -1076,7 +1076,7 @@
</para>
<para>
The Yocto Project supports a <link linkend='usingpoky-changes-layers'>"layers"</link> concept.
The Yocto Project supports a "<link linkend='usingpoky-changes-layers'>layers</link>" concept.
If you use layers properly, you can ease future upgrades and allow segregation
between the Yocto Project core and a given developer's changes.
The following section provides more advice on managing changes to the Yocto Project.
@@ -1321,7 +1321,7 @@
Experience shows that buildbot is a good fit for this role.
What works well is to configure buildbot to make two types of builds:
incremental and full (from scratch).
See <ulink url='&YOCTO_HOME_URL;:8010'>the buildbot for the
See <ulink url='&YOCTO_AB_URL;:8010'>the buildbot for the
Yocto Project</ulink> for an example implementation that uses buildbot.
</para>

View File

@@ -679,8 +679,8 @@
This variable must be defined for all recipes (unless <filename>LICENSE</filename>
is set to "CLOSED")</para>
<para>For more information, see the
<link linkend='usingpoky-configuring-LIC_FILES_CHKSUM'>
Track License Change</link> section</para>
"<link linkend='usingpoky-configuring-LIC_FILES_CHKSUM'>Track License Change</link>"
section</para>
</glossdef>
</glossentry>
@@ -849,7 +849,7 @@
<glossentry id='var-MACHINE_FEATURES'><glossterm>MACHINE_FEATURES</glossterm>
<glossdef>
<para>Specifies the list of device features.
See the <link linkend='ref-features-machine'>Machine</link> section for
See the "<link linkend='ref-features-machine'>Machine</link>" section for
more information.</para>
</glossdef>
</glossentry>
@@ -887,7 +887,7 @@
</literallayout>
For information on build performance effects as a result of the
package manager use, see
<link linkend='ref-classes-package'>Packaging - <filename>package*.bbclass</filename></link>
"<link linkend='ref-classes-package'>Packaging - <filename>package*.bbclass</filename></link>"
in this manual.
</para>
</glossdef>