summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRobert P. J. Day <rpjday@crashcourse.ca>2011-11-02 13:05:20 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-11-08 16:26:30 +0000
commit54956b8d506e42653d893764d5df27f1ce52a8be (patch)
tree195ab6f5a4954ecc5ac0c681ae7d25104b5052db
parent9f103615fb9d214dc7dc8a78f1980010577a2cc2 (diff)
downloadpoky-54956b8d506e42653d893764d5df27f1ce52a8be.tar.gz
documentation/dev-manual/dev-manual-start.xml: Robert P. J. Edits
Robert isolated a few technical errors and made some other wording suggestions. I took the technical corrections and modified one of his suggested wording changes. (From yocto-docs rev: 3c6bbae05cdf2265e04d967050354ce75d62b4e2) 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-start.xml8
1 files changed, 4 insertions, 4 deletions
diff --git a/documentation/dev-manual/dev-manual-start.xml b/documentation/dev-manual/dev-manual-start.xml
index a5f3652b13..e9342d0786 100644
--- a/documentation/dev-manual/dev-manual-start.xml
+++ b/documentation/dev-manual/dev-manual-start.xml
@@ -36,7 +36,7 @@
36 While the Yocto Project does not provide a strict testing framework, 36 While the Yocto Project does not provide a strict testing framework,
37 it does provide or generate for you artifacts that let you perform target-level and 37 it does provide or generate for you artifacts that let you perform target-level and
38 emulated testing and debugging. 38 emulated testing and debugging.
39 And, if you are an <trademark class='trade'>Eclipse</trademark> 39 Additionally, if you are an <trademark class='trade'>Eclipse</trademark>
40 IDE user, you can install an Eclipse Yocto Plug-in to allow you to 40 IDE user, you can install an Eclipse Yocto Plug-in to allow you to
41 develop within that familiar environment. 41 develop within that familiar environment.
42 </para> 42 </para>
@@ -77,7 +77,7 @@
77 Once you have the tarball, just extract it into a directory of your choice.</para> 77 Once you have the tarball, just extract it into a directory of your choice.</para>
78 <para>For example, the following command extracts the Yocto Project 1.1 release tarball 78 <para>For example, the following command extracts the Yocto Project 1.1 release tarball
79 into the current working directory and sets up the Yocto Project file structure 79 into the current working directory and sets up the Yocto Project file structure
80 with a top-level directory named <filename>poky-1.1</filename>: 80 with a top-level directory named <filename>poky-edison-6.0</filename>:
81 <literallayout class='monospaced'> 81 <literallayout class='monospaced'>
82 $ tar xfj poky-edison-6.0.tar.bz2 82 $ tar xfj poky-edison-6.0.tar.bz2
83 </literallayout></para> 83 </literallayout></para>
@@ -195,7 +195,7 @@
195 <filename>meta-intel</filename> 195 <filename>meta-intel</filename>
196 Git repository inside the <filename>poky</filename> Git repository. 196 Git repository inside the <filename>poky</filename> Git repository.
197 <literallayout class='monospaced'> 197 <literallayout class='monospaced'>
198 $cd poky 198 $ cd poky
199 $ git clone git://git.yoctoproject.org/meta-intel.git 199 $ git clone git://git.yoctoproject.org/meta-intel.git
200 Initialized empty Git repository in /home/scottrif/poky/meta-intel/.git/ 200 Initialized empty Git repository in /home/scottrif/poky/meta-intel/.git/
201 remote: Counting objects: 1325, done. 201 remote: Counting objects: 1325, done.
@@ -240,7 +240,7 @@
240 <listitem><para>Optionally ensure the <filename>conf/local.conf</filename> configuration file is set 240 <listitem><para>Optionally ensure the <filename>conf/local.conf</filename> configuration file is set
241 up how you want it. 241 up how you want it.
242 This file defines the target machine architecture and other build options.</para></listitem> 242 This file defines the target machine architecture and other build options.</para></listitem>
243 <listitem><para>Build the image using the BitBake command. 243 <listitem><para>Build the image using the <command>bitbake</command> command.
244 If you want information on Bitbake, see the user manual at 244 If you want information on Bitbake, see the user manual at
245 <ulink url='http://docs.openembedded.org/bitbake/html'></ulink>.</para></listitem> 245 <ulink url='http://docs.openembedded.org/bitbake/html'></ulink>.</para></listitem>
246 <listitem><para>Run the image either on the actual hardware or using the QEMU 246 <listitem><para>Run the image either on the actual hardware or using the QEMU