summaryrefslogtreecommitdiffstats
path: root/documentation/poky-ref-manual
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2010-11-09 13:14:00 -0800
committerRichard Purdie <rpurdie@linux.intel.com>2010-11-15 22:25:24 +0000
commit00b5b4dff7678efd86c69ba35d684c9cb4169beb (patch)
tree54d4328d1d02f17404f121aa598eb111a9cb7a97 /documentation/poky-ref-manual
parentd16bbc076a56be967b405f00a2d1b432992316e0 (diff)
downloadpoky-00b5b4dff7678efd86c69ba35d684c9cb4169beb.tar.gz
Poky Reference Manual: XML tag clean up and command example text indentation.
Removed a couple of redundant </ulink> tags. Also indented the literallayout text by five spaces for formatting. Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Diffstat (limited to 'documentation/poky-ref-manual')
-rw-r--r--documentation/poky-ref-manual/usingpoky.xml31
1 files changed, 17 insertions, 14 deletions
diff --git a/documentation/poky-ref-manual/usingpoky.xml b/documentation/poky-ref-manual/usingpoky.xml
index 4f75e1a279..fa08699129 100644
--- a/documentation/poky-ref-manual/usingpoky.xml
+++ b/documentation/poky-ref-manual/usingpoky.xml
@@ -66,7 +66,7 @@
66 Bitbake chooses the one selected by the distribution configuration. 66 Bitbake chooses the one selected by the distribution configuration.
67 You can get more details about how bitbake chooses between different versions 67 You can get more details about how bitbake chooses between different versions
68 and providers in the <link linkend='ref-bitbake-providers'> 68 and providers in the <link linkend='ref-bitbake-providers'>
69 'Preferences and Providers' section</link>. 69 'Preferences and Providers'</link> section.
70 </para> 70 </para>
71 <para> 71 <para>
72 Bitbake also tries to execute any dependent tasks first. 72 Bitbake also tries to execute any dependent tasks first.
@@ -131,8 +131,8 @@
131 </para> 131 </para>
132 <para> 132 <para>
133 <literallayout class='monospaced'> 133 <literallayout class='monospaced'>
134$ source poky-init-build-env [build_dir] 134 $ source poky-init-build-env [build_dir]
135</literallayout> 135 </literallayout>
136 </para> 136 </para>
137 <para> 137 <para>
138 The build_dir is the dir containing all the build's object files. The default 138 The build_dir is the dir containing all the build's object files. The default
@@ -146,8 +146,8 @@ $ source poky-init-build-env [build_dir]
146 </para> 146 </para>
147 <para> 147 <para>
148 <literallayout class='monospaced'> 148 <literallayout class='monospaced'>
149$ bitbake &lt;target&gt; 149 $ bitbake &lt;target&gt;
150</literallayout> 150 </literallayout>
151 </para> 151 </para>
152 <para> 152 <para>
153 The target is the name of the recipe you want to build. 153 The target is the name of the recipe you want to build.
@@ -169,7 +169,7 @@ $ bitbake &lt;target&gt;
169 <filename class="directory">tmp/deploy/images</filename> directory. 169 <filename class="directory">tmp/deploy/images</filename> directory.
170 Running qemux86 and qemuarm images is described in the 170 Running qemux86 and qemuarm images is described in the
171 'Using Pre-Built Binaries and QEMU' section of the Yocto Project Quick Start. 171 'Using Pre-Built Binaries and QEMU' section of the Yocto Project Quick Start.
172 See <ulink url="http://www.yoctoproject.org//docs/yocto-quick-start/yocto-project-qs.html"></ulink> 172 See <ulink url="http://www.yoctoproject.org//docs/yocto-quick-start/yocto-project-qs.html"/>
173 for the guide. 173 for the guide.
174 For information about how to install these images, see the documentation for your 174 For information about how to install these images, see the documentation for your
175 particular board/machine. 175 particular board/machine.
@@ -201,13 +201,16 @@ $ bitbake &lt;target&gt;
201 <filename>run.do_taskname.pid </filename> file located in the same directory. 201 <filename>run.do_taskname.pid </filename> file located in the same directory.
202 </para> 202 </para>
203 203
204 <para>Presently, the output from python tasks is sent directly to the console.</para> 204 <para>
205 Presently, the output from python tasks is sent directly to the console.
206 </para>
205 </section> 207 </section>
206 208
207 <section id='usingpoky-debugging-taskrunning'> 209 <section id='usingpoky-debugging-taskrunning'>
208 <title>Running Specific Tasks</title> 210 <title>Running Specific Tasks</title>
209 211
210 <para> Any given package consists of a set of tasks. 212 <para>
213 Any given package consists of a set of tasks.
211 In most cases the series is: fetch, unpack, patch, configure, 214 In most cases the series is: fetch, unpack, patch, configure,
212 compile, install, package, package_write and build. 215 compile, install, package, package_write and build.
213 The default task is "build" and any tasks on which it depends build first - hence, 216 The default task is "build" and any tasks on which it depends build first - hence,
@@ -216,7 +219,7 @@ $ bitbake &lt;target&gt;
216 If you wish to run a task that is not part of the default build chain you can use the 219 If you wish to run a task that is not part of the default build chain you can use the
217 "-c" option in bitbake as follows: 220 "-c" option in bitbake as follows:
218 <literallayout class='monospaced'> 221 <literallayout class='monospaced'>
219$ bitbake matchbox-desktop -c devshell 222 $ bitbake matchbox-desktop -c devshell
220 </literallayout> 223 </literallayout>
221 </para> 224 </para>
222 225
@@ -228,10 +231,10 @@ $ bitbake matchbox-desktop -c devshell
228 231
229 <para> 232 <para>
230 <literallayout class='monospaced'> 233 <literallayout class='monospaced'>
231$ bitbake matchbox-desktop 234 $ bitbake matchbox-desktop
232[make some changes to the source code in the WORKDIR] 235 [make some changes to the source code in the WORKDIR]
233$ bitbake matchbox-desktop -c compile -f 236 $ bitbake matchbox-desktop -c compile -f
234$ bitbake matchbox-desktop 237 $ bitbake matchbox-desktop
235 </literallayout> 238 </literallayout>
236 </para> 239 </para>
237 240
@@ -246,7 +249,7 @@ $ bitbake matchbox-desktop
246 You can view a list of tasks in a given package by running the listtasks task. 249 You can view a list of tasks in a given package by running the listtasks task.
247 For example: 250 For example:
248 <literallayout class='monospaced'> 251 <literallayout class='monospaced'>
249$ bitbake matchbox-desktop -c 252 $ bitbake matchbox-desktop -c
250 </literallayout> 253 </literallayout>
251 The results are in the file <filename>${WORKDIR}/temp/log.do_listtasks</filename>. 254 The results are in the file <filename>${WORKDIR}/temp/log.do_listtasks</filename>.
252 </para> 255 </para>