summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2012-06-14 21:41:22 (GMT)
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-06-29 13:59:25 (GMT)
commitc0433b3b9409610481d49f2563dbc57c8995dbf8 (patch)
treee9d4cb179d1935d55acb2282314abd05810b52c2
parent28989f2d048ca50b3df7b73ceda446b531cef73c (diff)
downloadpoky-c0433b3b9409610481d49f2563dbc57c8995dbf8.tar.gz
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>
-rw-r--r--documentation/dev-manual/dev-manual-bsp-appendix.xml4
-rw-r--r--documentation/dev-manual/dev-manual-intro.xml7
-rw-r--r--documentation/dev-manual/dev-manual-newbie.xml16
3 files changed, 14 insertions, 13 deletions
diff --git a/documentation/dev-manual/dev-manual-bsp-appendix.xml b/documentation/dev-manual/dev-manual-bsp-appendix.xml
index 74d5406..4d4bc01 100644
--- a/documentation/dev-manual/dev-manual-bsp-appendix.xml
+++ b/documentation/dev-manual/dev-manual-bsp-appendix.xml
@@ -161,11 +161,11 @@
161 <ulink url='&YOCTO_HOME_URL;/download'>Download</ulink> page of the 161 <ulink url='&YOCTO_HOME_URL;/download'>Download</ulink> page of the
162 Yocto Project website. 162 Yocto Project website.
163 Here is the specific link for the tarball needed for this example: 163 Here is the specific link for the tarball needed for this example:
164 <ulink url='&YOCTO_MACHINES_DL_URL;/crownbay-noemgd/crownbay-noemgd-&DISTRO_NAME;-&POKYVERSION;.tar.bz2'></ulink>. 164 <ulink url='&YOCTO_DL_URL;/releases/yocto/yocto-1.1/machines/crownbay-noemgd/crownbay-noemgd-edison-6.0.0.tar.bz2'></ulink>.
165 Again, be sure that you are already in the <filename>poky</filename> directory 165 Again, be sure that you are already in the <filename>poky</filename> directory
166 as described previously before installing the tarball: 166 as described previously before installing the tarball:
167 <literallayout class='monospaced'> 167 <literallayout class='monospaced'>
168 $ tar xfj crownbay-noemgd-&DISTRO_NAME;-&POKYVERSION;.tar.bz2 168 $ tar xfj crownbay-noemgd-&DISTRO_NAME;-6.0.0.tar.bz2
169 $ cd meta-intel 169 $ cd meta-intel
170 </literallayout> 170 </literallayout>
171 </para> 171 </para>
diff --git a/documentation/dev-manual/dev-manual-intro.xml b/documentation/dev-manual/dev-manual-intro.xml
index b9a6322..0728753 100644
--- a/documentation/dev-manual/dev-manual-intro.xml
+++ b/documentation/dev-manual/dev-manual-intro.xml
@@ -18,7 +18,8 @@
18 sources where you can find more detail. 18 sources where you can find more detail.
19 For example, detailed information on Git, repositories and open source in general 19 For example, detailed information on Git, repositories and open source in general
20 can be found in many places. 20 can be found in many places.
21 Another example is how to get set up to use the Yocto Project, which our Yocto Project Quick Start covers. 21 Another example is how to get set up to use the Yocto Project, which our
22 <ulink url='&YOCTO_DOCS_QS_URL;'>Yocto Project Quick Start</ulink> covers.
22 </para> 23 </para>
23 24
24 <para> 25 <para>
@@ -64,7 +65,9 @@
64 <itemizedlist> 65 <itemizedlist>
65 <listitem><para>Step-by-step instructions if those instructions exist in other Yocto 66 <listitem><para>Step-by-step instructions if those instructions exist in other Yocto
66 Project documentation. 67 Project documentation.
67 For example, the Application Development Toolkit (ADT) User’s Guide contains detailed 68 For example, the
69 <ulink url='&YOCTO_DOCS_ADT_URL;'>Yocto Project Application Development Toolkit (ADT)
70 User's Guide</ulink> contains detailed
68 instruction on how to obtain and configure the 71 instruction on how to obtain and configure the
69 <trademark class='trade'>Eclipse</trademark> Yocto Plug-in.</para></listitem> 72 <trademark class='trade'>Eclipse</trademark> Yocto Plug-in.</para></listitem>
70 <listitem><para>Reference material. 73 <listitem><para>Reference material.
diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml
index bc95a20..774ac3d 100644
--- a/documentation/dev-manual/dev-manual-newbie.xml
+++ b/documentation/dev-manual/dev-manual-newbie.xml
@@ -171,10 +171,8 @@
171 Images are the binary output that runs on specific hardware and for specific 171 Images are the binary output that runs on specific hardware and for specific
172 use cases. 172 use cases.
173 For a list of the supported image types that the Yocto Project provides, see the 173 For a list of the supported image types that the Yocto Project provides, see the
174 "<ulink url='http://www.yoctoproject.org/docs/1.1.1/poky-ref-manual/poky-ref-manual.html#ref-images'>Reference: Images</ulink>" 174 "<ulink url='&YOCTO_DOCS_REF_URL;#ref-images'>Reference: Images</ulink>"
175 appendix in 175 appendix in the Yocto Project Reference Manual.</para></listitem>
176 <ulink url='http://www.yoctoproject.org/docs/1.1.1/poky-ref-manual/poky-ref-manual.html'>
177 The Yocto Project Reference Manual</ulink>.</para></listitem>
178 <listitem><para><emphasis>Layer:</emphasis> A collection of recipes representing the core, 176 <listitem><para><emphasis>Layer:</emphasis> A collection of recipes representing the core,
179 a BSP, or an application stack.</para></listitem> 177 a BSP, or an application stack.</para></listitem>
180 <listitem><para><emphasis>Metadata:</emphasis> The files that BitBake parses when building an image. 178 <listitem><para><emphasis>Metadata:</emphasis> The files that BitBake parses when building an image.
@@ -217,14 +215,14 @@
217 system in order to do any development using the Yocto Project.</para> 215 system in order to do any development using the Yocto Project.</para>
218 <para>The name of the top-level directory of the Yocto Project file structure 216 <para>The name of the top-level directory of the Yocto Project file structure
219 is derived from the Yocto Project release tarball. 217 is derived from the Yocto Project release tarball.
220 For example, downloading and unpacking <filename>poky-edison-6.0.1.tar.bz2</filename> 218 For example, downloading and unpacking <filename>&YOCTO_POKY_TARBALL;</filename>
221 results in a Yocto Project file structure whose Yocto Project source directory is named 219 results in a Yocto Project file structure whose Yocto Project source directory is named
222 <filename>poky-edison-6.0.1</filename>. 220 <filename>&YOCTO_POKY;</filename>.
223 If you create a Git repository, then you can name the repository anything you like.</para> 221 If you create a Git repository, then you can name the repository anything you like.</para>
224 <para>You can find instruction on how to set up the Yocto Project files on your 222 <para>You can find instruction on how to set up the Yocto Project files on your
225 host development system by reading 223 host development system by reading
226 the 224 the
227 "<ulink url='http://www.yoctoproject.org/docs/1.1.1/dev-manual/dev-manual.html#getting-setup'>Getting 225 "<ulink url='&YOCTO_DOCS_DEV_URL;#getting-setup'>Getting
228 Setup</ulink>" section.</para></listitem> 226 Setup</ulink>" section.</para></listitem>
229 <listitem><para><emphasis>Yocto Project Build Directory:</emphasis> 227 <listitem><para><emphasis>Yocto Project Build Directory:</emphasis>
230 This term refers to the area used by the Yocto Project for builds. 228 This term refers to the area used by the Yocto Project for builds.
@@ -234,9 +232,9 @@
234 You can create the Yocto Project build directory anywhere you want on your 232 You can create the Yocto Project build directory anywhere you want on your
235 development system. 233 development system.
236 Here is an example that creates the directory in <filename>mybuilds</filename> 234 Here is an example that creates the directory in <filename>mybuilds</filename>
237 and names the Yocto Project build directory <filename>YP-6.0.1</filename>: 235 and names the Yocto Project build directory <filename>YP-&POKYVERSION;</filename>:
238 <literallayout class='monospaced'> 236 <literallayout class='monospaced'>
239 $ source poky-edison-6.0.1/oe-init-build-env $HOME/mybuilds/YP-6.0.1 237 $ source &OE_INIT_PATH; $HOME/mybuilds/YP-&POKYVERSION;
240 </literallayout> 238 </literallayout>
241 If you don't specifically name the directory, BitBake creates it 239 If you don't specifically name the directory, BitBake creates it
242 in the current directory and uses the name <filename>build</filename>. 240 in the current directory and uses the name <filename>build</filename>.