From 953ad50a273bce512e679a9caa5050419989f414 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Thu, 14 Jun 2012 07:38:09 -0700 Subject: 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 Signed-off-by: Richard Purdie --- documentation/poky-ref-manual/development.xml | 30 ++++++++++++------------- documentation/poky-ref-manual/extendpoky.xml | 4 ++-- documentation/poky-ref-manual/ref-variables.xml | 8 +++---- 3 files changed, 20 insertions(+), 22 deletions(-) diff --git a/documentation/poky-ref-manual/development.xml b/documentation/poky-ref-manual/development.xml index 76a0423f65..1fa31f005f 100644 --- a/documentation/poky-ref-manual/development.xml +++ b/documentation/poky-ref-manual/development.xml @@ -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 - under IDE Plugins. + under IDE Plugins. The community is free to continue supporting it beyond the Yocto Project 0.9 Release. @@ -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 - - "Working Within Eclipse" chapter in the - - "Application Development Toolkit (ADT) User's Guide." + "Working Within Eclipse" chapter in the + Yocto Project Application Development Toolkit (ADT) User's Guide. @@ -103,8 +101,8 @@ External Development Using the QEMU Emulator Running Poky QEMU images is covered in the - - Yocto Project Quick Start in the "A Quick Test Run" section. + "A Quick Test Run" section of + the Yocto Project Quick Start. The QEMU images shipped with the Yocto Project contain complete toolchains @@ -163,8 +161,8 @@ 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 - (WORKDIR) - or the source directory (S) + (WORKDIR) + or the source directory (S) 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 @@ It is useful when making changes directly to the work directory files to do so using the Quilt tool as detailed in the - - Modifying Package Source Code with Quilt section. + "Modifying Package Source Code with Quilt" + section. Using Quilt, you can copy patches into the recipe directory and use the patches directly - through use of the SRC_URI variable. + through use of the SRC_URI variable. For a review of the skills used in this section, see the - BitBake and - Running Specific Tasks sections + "BitBake" and + "Running Specific Tasks" sections in this manual. @@ -273,8 +271,8 @@ The default shell used by devshell is xterm. You can use other terminal forms by setting the - TERMCMD and - TERMCMDRUN variables + TERMCMD and + TERMCMDRUN variables in the Yocto Project's local.conf file found in the build directory. For examples of the other options available, see the "UI/Interaction Configuration" diff --git a/documentation/poky-ref-manual/extendpoky.xml b/documentation/poky-ref-manual/extendpoky.xml index c16e0f116c..234be80086 100644 --- a/documentation/poky-ref-manual/extendpoky.xml +++ b/documentation/poky-ref-manual/extendpoky.xml @@ -1076,7 +1076,7 @@ - The Yocto Project supports a "layers" concept. + The Yocto Project supports a "layers" 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 the buildbot for the + See the buildbot for the Yocto Project for an example implementation that uses buildbot. diff --git a/documentation/poky-ref-manual/ref-variables.xml b/documentation/poky-ref-manual/ref-variables.xml index 8e4d9df41c..cc4a87447a 100644 --- a/documentation/poky-ref-manual/ref-variables.xml +++ b/documentation/poky-ref-manual/ref-variables.xml @@ -679,8 +679,8 @@ This variable must be defined for all recipes (unless LICENSE is set to "CLOSED") For more information, see the - - Track License Change section + "Track License Change" + section @@ -849,7 +849,7 @@ MACHINE_FEATURES Specifies the list of device features. - See the Machine section for + See the "Machine" section for more information. @@ -887,7 +887,7 @@ For information on build performance effects as a result of the package manager use, see - Packaging - package*.bbclass + "Packaging - package*.bbclass" in this manual. -- cgit v1.2.3-54-g00ecf