From c0433b3b9409610481d49f2563dbc57c8995dbf8 Mon Sep 17 00:00:00 2001
From: Scott Rifenbark <scott.m.rifenbark@intel.com>
Date: Thu, 14 Jun 2012 14:41:22 -0700
Subject: documentation/dev-manual: Minor 1.1.2 updates

The second pass through the manual testing against the variables
put in during the first pass.  Minor changes and few links not
right.  One thing of note is the tarball used for the BSP appendix
example for Crown Bay.  The tarball I have in there is the
release 1.1 version with poky 6.0.0.

(From yocto-docs rev: 3839c0b0a063fd240b129c745ee95047a6e23cb8)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
 documentation/dev-manual/dev-manual-newbie.xml | 16 +++++++---------
 1 file changed, 7 insertions(+), 9 deletions(-)

(limited to 'documentation/dev-manual/dev-manual-newbie.xml')

diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml
index bc95a20c2a..774ac3d5bf 100644
--- a/documentation/dev-manual/dev-manual-newbie.xml
+++ b/documentation/dev-manual/dev-manual-newbie.xml
@@ -171,10 +171,8 @@
             Images are the binary output that runs on specific hardware and for specific
             use cases.
             For a list of the supported image types that the Yocto Project provides, see the
-            "<ulink url='http://www.yoctoproject.org/docs/1.1.1/poky-ref-manual/poky-ref-manual.html#ref-images'>Reference: Images</ulink>"
-            appendix in
-            <ulink url='http://www.yoctoproject.org/docs/1.1.1/poky-ref-manual/poky-ref-manual.html'>
-            The Yocto Project Reference Manual</ulink>.</para></listitem>
+            "<ulink url='&YOCTO_DOCS_REF_URL;#ref-images'>Reference: Images</ulink>"
+            appendix in the Yocto Project Reference Manual.</para></listitem>
         <listitem><para><emphasis>Layer:</emphasis> A collection of recipes representing the core, 
             a BSP, or an application stack.</para></listitem>
         <listitem><para><emphasis>Metadata:</emphasis> The files that BitBake parses when building an image. 
@@ -217,14 +215,14 @@
             system in order to do any development using the Yocto Project.</para>
             <para>The name of the top-level directory of the Yocto Project file structure  
             is derived from the Yocto Project release tarball.
-            For example, downloading and unpacking <filename>poky-edison-6.0.1.tar.bz2</filename>
+            For example, downloading and unpacking <filename>&YOCTO_POKY_TARBALL;</filename>
             results in a Yocto Project file structure whose Yocto Project source directory is named 
-            <filename>poky-edison-6.0.1</filename>.
+            <filename>&YOCTO_POKY;</filename>.
             If you create a Git repository, then you can name the repository anything you like.</para>
             <para>You can find instruction on how to set up the Yocto Project files on your 
             host development system by reading 
             the 
-            "<ulink url='http://www.yoctoproject.org/docs/1.1.1/dev-manual/dev-manual.html#getting-setup'>Getting
+            "<ulink url='&YOCTO_DOCS_DEV_URL;#getting-setup'>Getting
             Setup</ulink>" section.</para></listitem>
         <listitem><para><emphasis>Yocto Project Build Directory:</emphasis>
             This term refers to the area used by the Yocto Project for builds.  
@@ -234,9 +232,9 @@
             You can create the Yocto Project build directory anywhere you want on your 
             development system.
             Here is an example that creates the directory in <filename>mybuilds</filename> 
-            and names the Yocto Project build directory <filename>YP-6.0.1</filename>:
+            and names the Yocto Project build directory <filename>YP-&POKYVERSION;</filename>:
             <literallayout class='monospaced'> 
-     $ source poky-edison-6.0.1/oe-init-build-env $HOME/mybuilds/YP-6.0.1
+     $ source &OE_INIT_PATH; $HOME/mybuilds/YP-&POKYVERSION;
             </literallayout>
             If you don't specifically name the directory, BitBake creates it 
             in the current directory and uses the name <filename>build</filename>.
-- 
cgit v1.2.3-54-g00ecf