summaryrefslogtreecommitdiffstats
path: root/documentation/poky-ref-manual/usingpoky.xml
diff options
context:
space:
mode:
authorRobert P. J. Day <rpjday@crashcourse.ca>2011-11-09 07:58:24 -0800
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-11-25 15:24:16 +0000
commitc8fd49ab900d8f71d86f6045b655e26e0290ac9b (patch)
treedff5d6c85c068aac9effe55c1a6ce6388c7fa945 /documentation/poky-ref-manual/usingpoky.xml
parent90aff1ce68bfd66eb3fef337b29aa87179a01e4f (diff)
downloadpoky-c8fd49ab900d8f71d86f6045b655e26e0290ac9b.tar.gz
documentation/poky-ref-manual: Minor wording fixes
Robert identified several wording issues. Fixes applied. (From yocto-docs rev: 9c1ed58a1ecdd620246970419ed58b53f95cf2ec) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/poky-ref-manual/usingpoky.xml')
-rw-r--r--documentation/poky-ref-manual/usingpoky.xml10
1 files changed, 5 insertions, 5 deletions
diff --git a/documentation/poky-ref-manual/usingpoky.xml b/documentation/poky-ref-manual/usingpoky.xml
index 7b24841ac0..70573ef045 100644
--- a/documentation/poky-ref-manual/usingpoky.xml
+++ b/documentation/poky-ref-manual/usingpoky.xml
@@ -16,7 +16,7 @@
16 The BitBake task executor together with various types of configuration files form the 16 The BitBake task executor together with various types of configuration files form the
17 Yocto Project core. 17 Yocto Project core.
18 This section overviews the BitBake task executor and the 18 This section overviews the BitBake task executor and the
19 configuration files by describing what they are used for and they they interact. 19 configuration files by describing what they are used for and how they interact.
20 </para> 20 </para>
21 21
22 <para> 22 <para>
@@ -29,7 +29,7 @@
29 information (e.g. how to build a Linux kernel).</para></listitem> 29 information (e.g. how to build a Linux kernel).</para></listitem>
30 <listitem><para><emphasis>Configuration Data:</emphasis> Defines machine-specific settings, 30 <listitem><para><emphasis>Configuration Data:</emphasis> Defines machine-specific settings,
31 policy decisions, etc. 31 policy decisions, etc.
32 Configuration data acts a the glue to bind everything together.</para></listitem> 32 Configuration data acts as the glue to bind everything together.</para></listitem>
33 </itemizedlist> 33 </itemizedlist>
34 For more information on data, see the 34 For more information on data, see the
35 <ulink url='http://www.yoctoproject.org/docs/1.1/dev-manual/dev-manual.html#yocto-project-terms'> 35 <ulink url='http://www.yoctoproject.org/docs/1.1/dev-manual/dev-manual.html#yocto-project-terms'>
@@ -164,7 +164,7 @@
164 The first thing you need to do is set up the Yocto Project build environment by sourcing 164 The first thing you need to do is set up the Yocto Project build environment by sourcing
165 the environment setup script as follows: 165 the environment setup script as follows:
166 <literallayout class='monospaced'> 166 <literallayout class='monospaced'>
167 $ source oe-init-build-env [build_dir]; 167 $ source oe-init-build-env [build_dir]
168 </literallayout> 168 </literallayout>
169 </para> 169 </para>
170 170
@@ -172,7 +172,7 @@
172 The <filename>build_dir</filename> is optional and specifies the directory Yocto Project 172 The <filename>build_dir</filename> is optional and specifies the directory Yocto Project
173 uses for the build. 173 uses for the build.
174 If you do not specify a build directory it defaults to <filename>build</filename> 174 If you do not specify a build directory it defaults to <filename>build</filename>
175 in the Yocto Project files directory structure. 175 in your current working directory.
176 A common practice is to use a different build directory for different targets. 176 A common practice is to use a different build directory for different targets.
177 For example, <filename>~/build/x86</filename> for a <filename>qemux86</filename> 177 For example, <filename>~/build/x86</filename> for a <filename>qemux86</filename>
178 target, and <filename>~/build/arm</filename> for a <filename>qemuarm</filename> target. 178 target, and <filename>~/build/arm</filename> for a <filename>qemuarm</filename> target.
@@ -310,7 +310,7 @@
310 You can view a list of tasks in a given package by running the 310 You can view a list of tasks in a given package by running the
311 <filename>listtasks</filename> task as follows: 311 <filename>listtasks</filename> task as follows:
312 <literallayout class='monospaced'> 312 <literallayout class='monospaced'>
313 $ bitbake matchbox-desktop -c 313 $ bitbake matchbox-desktop -c listtasks
314 </literallayout> 314 </literallayout>
315 The results are in the file <filename>${WORKDIR}/temp/log.do_listtasks</filename>. 315 The results are in the file <filename>${WORKDIR}/temp/log.do_listtasks</filename>.
316 </para> 316 </para>