summaryrefslogtreecommitdiffstats
path: root/documentation/poky-ref-manual/ref-bitbake.xml
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/poky-ref-manual/ref-bitbake.xml')
-rw-r--r--documentation/poky-ref-manual/ref-bitbake.xml16
1 files changed, 8 insertions, 8 deletions
diff --git a/documentation/poky-ref-manual/ref-bitbake.xml b/documentation/poky-ref-manual/ref-bitbake.xml
index ed6c8bc15b..6221a963d8 100644
--- a/documentation/poky-ref-manual/ref-bitbake.xml
+++ b/documentation/poky-ref-manual/ref-bitbake.xml
@@ -3,10 +3,10 @@
3 3
4<appendix id='ref-bitbake'> 4<appendix id='ref-bitbake'>
5 5
6 <title>Reference: Bitbake</title> 6 <title>Reference: BitBake</title>
7 7
8 <para> 8 <para>
9 Bitbake is a program written in Python that interprets the metadata 9 BitBake is a program written in Python that interprets the metadata
10 that makes up Poky. At some point, people wonder what actually happens 10 that makes up Poky. At some point, people wonder what actually happens
11 when you type <command>bitbake poky-image-sato</command>. This section 11 when you type <command>bitbake poky-image-sato</command>. This section
12 aims to give an overview of what happens behind the scenes from a 12 aims to give an overview of what happens behind the scenes from a
@@ -14,7 +14,7 @@
14 </para> 14 </para>
15 15
16 <para> 16 <para>
17 It is worth noting that bitbake aims to be a generic "task" executor 17 It is worth noting that BitBake aims to be a generic "task" executor
18 capable of handling complex dependency relationships. As such it has no 18 capable of handling complex dependency relationships. As such it has no
19 real knowledge of what the tasks it is executing actually do. It just 19 real knowledge of what the tasks it is executing actually do. It just
20 considers a list of tasks with dependencies and handles metadata 20 considers a list of tasks with dependencies and handles metadata
@@ -28,7 +28,7 @@
28 <para> 28 <para>
29 The first thing BitBake does is work out its configuration by 29 The first thing BitBake does is work out its configuration by
30 looking for a file called <filename>bitbake.conf</filename>. 30 looking for a file called <filename>bitbake.conf</filename>.
31 Bitbake searches through the <varname>BBPATH</varname> environment 31 BitBake searches through the <varname>BBPATH</varname> environment
32 variable looking for a <filename class="directory">conf/</filename> 32 variable looking for a <filename class="directory">conf/</filename>
33 directory containing a <filename>bitbake.conf</filename> file and 33 directory containing a <filename>bitbake.conf</filename> file and
34 adds the first <filename>bitbake.conf</filename> file found in 34 adds the first <filename>bitbake.conf</filename> file found in
@@ -83,12 +83,12 @@
83 <filename class="directory">meta-extras/</filename> can be included 83 <filename class="directory">meta-extras/</filename> can be included
84 too. Adding extra content to 84 too. Adding extra content to
85 <glossterm><link linkend='var-BBFILES'>BBFILES</link></glossterm> is best 85 <glossterm><link linkend='var-BBFILES'>BBFILES</link></glossterm> is best
86 acheived through the use of Bitbake 86 acheived through the use of BitBake
87 <link linkend='usingpoky-changes-layers'>"layers"</link>. 87 <link linkend='usingpoky-changes-layers'>"layers"</link>.
88 </para> 88 </para>
89 89
90 <para> 90 <para>
91 Bitbake parses each <filename class="extension">.bb</filename> file in 91 BitBake parses each <filename class="extension">.bb</filename> file in
92 <glossterm><link linkend='var-BBFILES'>BBFILES</link></glossterm> and 92 <glossterm><link linkend='var-BBFILES'>BBFILES</link></glossterm> and
93 stores the values of various variables. In summary, for each 93 stores the values of various variables. In summary, for each
94 <filename class="extension">.bb</filename> 94 <filename class="extension">.bb</filename>
@@ -138,7 +138,7 @@
138 138
139 <para> 139 <para>
140 Understanding how providers are chosen is complicated by the fact 140 Understanding how providers are chosen is complicated by the fact
141 multiple versions might be present. Bitbake defaults to the highest 141 multiple versions might be present. BitBake defaults to the highest
142 version of a provider by default. Version comparisons are made using 142 version of a provider by default. Version comparisons are made using
143 the same method as Debian. The <glossterm><link 143 the same method as Debian. The <glossterm><link
144 linkend='var-PREFERRED_VERSION'>PREFERRED_VERSION</link></glossterm> 144 linkend='var-PREFERRED_VERSION'>PREFERRED_VERSION</link></glossterm>
@@ -316,7 +316,7 @@ Options:
316 316
317 <para> 317 <para>
318 As well as the containing the parsing and task/dependency handling 318 As well as the containing the parsing and task/dependency handling
319 code, bitbake also contains a set of "fetcher" modules which allow 319 code, BitBake also contains a set of "fetcher" modules which allow
320 fetching of source code from various types of sources. Example 320 fetching of source code from various types of sources. Example
321 sources might be from disk with the metadata, from websites, from 321 sources might be from disk with the metadata, from websites, from
322 remote shell accounts or from SCM systems like cvs/subversion/git. 322 remote shell accounts or from SCM systems like cvs/subversion/git.