summaryrefslogtreecommitdiffstats
path: root/documentation/poky-ref-manual/usingpoky.xml
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/poky-ref-manual/usingpoky.xml')
-rw-r--r--documentation/poky-ref-manual/usingpoky.xml32
1 files changed, 16 insertions, 16 deletions
diff --git a/documentation/poky-ref-manual/usingpoky.xml b/documentation/poky-ref-manual/usingpoky.xml
index 79e9dfbf9c..2d2e3f6eac 100644
--- a/documentation/poky-ref-manual/usingpoky.xml
+++ b/documentation/poky-ref-manual/usingpoky.xml
@@ -5,7 +5,7 @@
5 5
6 <para> 6 <para>
7 This section gives an overview of the components that make up Poky 7 This section gives an overview of the components that make up Poky
8 following by information about running poky builds and dealing with any 8 followed by information about running poky builds and dealing with any
9 problems that may arise. 9 problems that may arise.
10 </para> 10 </para>
11 11
@@ -13,8 +13,8 @@
13 <title>Poky Overview</title> 13 <title>Poky Overview</title>
14 14
15 <para> 15 <para>
16 The bitbake task executor together with various types of configuration files form the core of Poky. 16 The BitBake task executor together with various types of configuration files form the core of Poky.
17 This section overviews the bitbake task executor and the 17 This section overviews the BitBake task executor and the
18 configuration files by describing what they are used for and they they interact. 18 configuration files by describing what they are used for and they they interact.
19 </para> 19 </para>
20 20
@@ -48,12 +48,12 @@
48 <para> 48 <para>
49 Bitbake is the tool at the heart of Poky and is responsible 49 Bitbake is the tool at the heart of Poky and is responsible
50 for parsing the metadata, generating a list of tasks from it 50 for parsing the metadata, generating a list of tasks from it
51 and then executing them. To see a list of the options bitbake 51 and then executing them. To see a list of the options BitBake
52 supports look at 'bitbake --help'. 52 supports look at 'bitbake --help'.
53 </para> 53 </para>
54 54
55 <para> 55 <para>
56 The most common usage for bitbake is <filename>bitbake &lt;packagename&gt;</filename>, where 56 The most common usage for BitBake is <filename>bitbake &lt;packagename&gt;</filename>, where
57 packagename is the name of the package you want to build (referred to as the 'target' 57 packagename is the name of the package you want to build (referred to as the 'target'
58 in this manual). 58 in this manual).
59 The target often equates to the first part of a <filename>.bb</filename> filename. 59 The target often equates to the first part of a <filename>.bb</filename> filename.
@@ -64,13 +64,13 @@
64 </literallayout> 64 </literallayout>
65 Several different versions of <filename>matchbox-desktop</filename> might exist. 65 Several different versions of <filename>matchbox-desktop</filename> might exist.
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'</link> section. 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.
73 So for example, before building <filename>matchbox-desktop</filename> bitbake 73 So for example, before building <filename>matchbox-desktop</filename> BitBake
74 would build a cross compiler and glibc if they had not already been built. 74 would build a cross compiler and glibc if they had not already been built.
75 </para> 75 </para>
76 76
@@ -197,7 +197,7 @@
197 <para>The log file for shell tasks is available in <filename>${WORKDIR}/temp/log.do_taskname.pid</filename>. 197 <para>The log file for shell tasks is available in <filename>${WORKDIR}/temp/log.do_taskname.pid</filename>.
198 For example, the "compile" task of busybox 1.01 on the ARM spitz machine might be 198 For example, the "compile" task of busybox 1.01 on the ARM spitz machine might be
199 <filename>tmp/work/armv5te-poky-linux-gnueabi/busybox-1.01/temp/log.do_compile.1234</filename>. 199 <filename>tmp/work/armv5te-poky-linux-gnueabi/busybox-1.01/temp/log.do_compile.1234</filename>.
200 To see what bitbake runs to generate that log, look at the corresponding 200 To see what BitBake runs to generate that log, look at the corresponding
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
@@ -214,10 +214,10 @@
214 In most cases the series is: fetch, unpack, patch, configure, 214 In most cases the series is: fetch, unpack, patch, configure,
215 compile, install, package, package_write and build. 215 compile, install, package, package_write and build.
216 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,
217 the standard bitbake behaviour. 217 the standard BitBake behaviour.
218 Some tasks exist, such as devshell, that are not part of the default build chain. 218 Some tasks exist, such as devshell, that are not part of the default build chain.
219 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
220 "-c" option in bitbake as follows: 220 "-c" option in BitBake as follows:
221 <literallayout class='monospaced'> 221 <literallayout class='monospaced'>
222 $ bitbake matchbox-desktop -c devshell 222 $ bitbake matchbox-desktop -c devshell
223 </literallayout> 223 </literallayout>
@@ -259,7 +259,7 @@
259 <title>Dependency Graphs</title> 259 <title>Dependency Graphs</title>
260 260
261 <para> 261 <para>
262 Sometimes it can be hard to see why bitbake wants to build some other packages before a given 262 Sometimes it can be hard to see why BitBake wants to build some other packages before a given
263 package you've specified. 263 package you've specified.
264 The <filename>bitbake -g targetname</filename> command creates the <filename>depends.dot</filename> and 264 The <filename>bitbake -g targetname</filename> command creates the <filename>depends.dot</filename> and
265 <filename>task-depends.dot</filename> files in the current directory. 265 <filename>task-depends.dot</filename> files in the current directory.
@@ -273,8 +273,8 @@
273 <title>General Bitbake Problems</title> 273 <title>General Bitbake Problems</title>
274 274
275 <para> 275 <para>
276 You can see debug output from bitbake by using the "-D" option. 276 You can see debug output from BitBake by using the "-D" option.
277 The debug output gives more information about what bitbake 277 The debug output gives more information about what BitBake
278 is doing and the reason behind it. 278 is doing and the reason behind it.
279 Each "-D" option you use increases the logging level. 279 Each "-D" option you use increases the logging level.
280 The most common usage is <filename>-DDD</filename>. 280 The most common usage is <filename>-DDD</filename>.
@@ -282,9 +282,9 @@
282 282
283 <para> 283 <para>
284 The output from <filename>bitbake -DDD -v targetname</filename> can reveal why 284 The output from <filename>bitbake -DDD -v targetname</filename> can reveal why
285 bitbake chose a certain version of a package or why bitbake 285 BitBake chose a certain version of a package or why BitBake
286 picked a certain provider. 286 picked a certain provider.
287 This command could also help you in a situation where you think bitbake did something 287 This command could also help you in a situation where you think BitBake did something
288 unexpected. 288 unexpected.
289 </para> 289 </para>
290 </section> 290 </section>
@@ -296,7 +296,7 @@
296 the command form <filename>bitbake -b somepath/somefile.bb</filename>. 296 the command form <filename>bitbake -b somepath/somefile.bb</filename>.
297 This command form does not check for dependencies so you should use it 297 This command form does not check for dependencies so you should use it
298 only when you know its dependencies already exist. 298 only when you know its dependencies already exist.
299 You can also specify fragments of the filename and bitbake checks for a unique match. 299 You can also specify fragments of the filename and BitBake checks for a unique match.
300 </para> 300 </para>
301 </section> 301 </section>
302 302