diff options
Diffstat (limited to 'documentation/ref-manual/usingpoky.xml')
-rw-r--r-- | documentation/ref-manual/usingpoky.xml | 26 |
1 files changed, 13 insertions, 13 deletions
diff --git a/documentation/ref-manual/usingpoky.xml b/documentation/ref-manual/usingpoky.xml index 283fb725ac..1a211ca78a 100644 --- a/documentation/ref-manual/usingpoky.xml +++ b/documentation/ref-manual/usingpoky.xml | |||
@@ -35,12 +35,12 @@ | |||
35 | <link linkend='structure-memres-core-script'><filename>oe-init-build-env-memres</filename></link>). | 35 | <link linkend='structure-memres-core-script'><filename>oe-init-build-env-memres</filename></link>). |
36 | Here is an example: | 36 | Here is an example: |
37 | <literallayout class='monospaced'> | 37 | <literallayout class='monospaced'> |
38 | $ source &OE_INIT_FILE; [<build_dir>] | 38 | $ source &OE_INIT_FILE; [<replaceable>build_dir</replaceable>] |
39 | </literallayout> | 39 | </literallayout> |
40 | </para> | 40 | </para> |
41 | 41 | ||
42 | <para> | 42 | <para> |
43 | The <filename>build_dir</filename> argument is optional and specifies the directory the | 43 | The <replaceable>build_dir</replaceable> argument is optional and specifies the directory the |
44 | OpenEmbedded build system uses for the build - | 44 | OpenEmbedded build system uses for the build - |
45 | the <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>. | 45 | the <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>. |
46 | If you do not specify a Build Directory, it defaults to a directory | 46 | If you do not specify a Build Directory, it defaults to a directory |
@@ -53,12 +53,12 @@ | |||
53 | <para> | 53 | <para> |
54 | Once the build environment is set up, you can build a target using: | 54 | Once the build environment is set up, you can build a target using: |
55 | <literallayout class='monospaced'> | 55 | <literallayout class='monospaced'> |
56 | $ bitbake <target> | 56 | $ bitbake <replaceable>target</replaceable> |
57 | </literallayout> | 57 | </literallayout> |
58 | </para> | 58 | </para> |
59 | 59 | ||
60 | <para> | 60 | <para> |
61 | The <filename>target</filename> is the name of the recipe you want to build. | 61 | The <replaceable>target</replaceable> is the name of the recipe you want to build. |
62 | Common targets are the images in <filename>meta/recipes-core/images</filename>, | 62 | Common targets are the images in <filename>meta/recipes-core/images</filename>, |
63 | <filename>meta/recipes-sato/images</filename>, etc. all found in the | 63 | <filename>meta/recipes-sato/images</filename>, etc. all found in the |
64 | <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>. | 64 | <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>. |
@@ -154,14 +154,14 @@ | |||
154 | <title>Task Failures</title> | 154 | <title>Task Failures</title> |
155 | 155 | ||
156 | <para>The log file for shell tasks is available in | 156 | <para>The log file for shell tasks is available in |
157 | <filename>${WORKDIR}/temp/log.do_taskname.pid</filename>. | 157 | <filename>${WORKDIR}/temp/log.do_<replaceable>taskname</replaceable>.pid</filename>. |
158 | For example, the <filename>compile</filename> task for the QEMU minimal image for the x86 | 158 | For example, the <filename>do_compile</filename> task for the QEMU minimal image for the x86 |
159 | machine (<filename>qemux86</filename>) might be | 159 | machine (<filename>qemux86</filename>) might be |
160 | <filename>tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/temp/log.do_compile.20830</filename>. | 160 | <filename>tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/temp/log.do_compile.20830</filename>. |
161 | To see what | 161 | To see what |
162 | <ulink url='&YOCTO_DOCS_DEV_URL;#bitbake-term'>BitBake</ulink> | 162 | <ulink url='&YOCTO_DOCS_DEV_URL;#bitbake-term'>BitBake</ulink> |
163 | runs to generate that log, look at the corresponding | 163 | runs to generate that log, look at the corresponding |
164 | <filename>run.do_taskname.pid</filename> file located in the same directory. | 164 | <filename>run.do_<replaceable>taskname</replaceable>.pid</filename> file located in the same directory. |
165 | </para> | 165 | </para> |
166 | 166 | ||
167 | <para> | 167 | <para> |
@@ -203,7 +203,7 @@ | |||
203 | $ bitbake matchbox-desktop | 203 | $ bitbake matchbox-desktop |
204 | . | 204 | . |
205 | . | 205 | . |
206 | [make some changes to the source code in the work directory] | 206 | <replaceable>make some changes to the source code in the work directory</replaceable> |
207 | . | 207 | . |
208 | . | 208 | . |
209 | $ bitbake matchbox-desktop -c compile -f | 209 | $ bitbake matchbox-desktop -c compile -f |
@@ -238,7 +238,7 @@ | |||
238 | <para> | 238 | <para> |
239 | Sometimes it can be hard to see why BitBake wants to build | 239 | Sometimes it can be hard to see why BitBake wants to build |
240 | other packages before building a given package you have specified. | 240 | other packages before building a given package you have specified. |
241 | The <filename>bitbake -g <targetname></filename> command | 241 | The <filename>bitbake -g <replaceable>targetname</replaceable></filename> command |
242 | creates the <filename>pn-buildlist</filename>, | 242 | creates the <filename>pn-buildlist</filename>, |
243 | <filename>pn-depends.dot</filename>, | 243 | <filename>pn-depends.dot</filename>, |
244 | <filename>package-depends.dot</filename>, and | 244 | <filename>package-depends.dot</filename>, and |
@@ -247,7 +247,7 @@ | |||
247 | These files show what will be built and the package and task | 247 | These files show what will be built and the package and task |
248 | dependencies, which are useful for debugging problems. | 248 | dependencies, which are useful for debugging problems. |
249 | You can use the | 249 | You can use the |
250 | <filename>bitbake -g -u depexp <targetname></filename> | 250 | <filename>bitbake -g -u depexp <replaceable>targetname</replaceable></filename> |
251 | command to display the results in a more human-readable form. | 251 | command to display the results in a more human-readable form. |
252 | </para> | 252 | </para> |
253 | </section> | 253 | </section> |
@@ -264,7 +264,7 @@ | |||
264 | </para> | 264 | </para> |
265 | 265 | ||
266 | <para> | 266 | <para> |
267 | The output from <filename>bitbake -DDD -v targetname</filename> can reveal why | 267 | The output from <filename>bitbake -DDD -v</filename> <replaceable>targetname</replaceable> can reveal why |
268 | BitBake chose a certain version of a package or why BitBake | 268 | BitBake chose a certain version of a package or why BitBake |
269 | picked a certain provider. | 269 | picked a certain provider. |
270 | This command could also help you in a situation where you think BitBake did something | 270 | This command could also help you in a situation where you think BitBake did something |
@@ -310,7 +310,7 @@ | |||
310 | To build a specific recipe (<filename>.bb</filename> file), | 310 | To build a specific recipe (<filename>.bb</filename> file), |
311 | you can use the following command form: | 311 | you can use the following command form: |
312 | <literallayout class='monospaced'> | 312 | <literallayout class='monospaced'> |
313 | $ bitbake -b <somepath/somerecipe.bb> | 313 | $ bitbake -b <replaceable>somepath</replaceable>/<replaceable>somerecipe</replaceable>.bb |
314 | </literallayout> | 314 | </literallayout> |
315 | This command form does not check for dependencies. | 315 | This command form does not check for dependencies. |
316 | Consequently, you should use it | 316 | Consequently, you should use it |
@@ -334,7 +334,7 @@ | |||
334 | This next example shows the parsing environment for a specific | 334 | This next example shows the parsing environment for a specific |
335 | recipe: | 335 | recipe: |
336 | <literallayout class='monospaced'> | 336 | <literallayout class='monospaced'> |
337 | $ bitbake -e <recipename> | 337 | $ bitbake -e <replaceable>recipename</replaceable> |
338 | </literallayout> | 338 | </literallayout> |
339 | </para> | 339 | </para> |
340 | </section> | 340 | </section> |