summaryrefslogtreecommitdiff
path: root/documentation
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2011-03-17 16:46:38 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-03-18 17:20:45 +0000
commit982826b61bf68244fad46ef52b5a203e648e330b (patch)
tree085c6634a235b059ef33a717b3ffedf899a8b44f /documentation
parenta25074cf7f3383ea3963c4dabb9507af34f2e3df (diff)
downloadopenembedded-core-982826b61bf68244fad46ef52b5a203e648e330b.tar.gz
openembedded-core-982826b61bf68244fad46ef52b5a203e648e330b.tar.bz2
openembedded-core-982826b61bf68244fad46ef52b5a203e648e330b.zip
documentation/poky-ref-manual/usingpoky.xml: More BitBake changes
Forgot to search for "Bitbake" occurances. These are now changed to "BitBake." Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Diffstat (limited to 'documentation')
-rw-r--r--documentation/poky-ref-manual/usingpoky.xml16
1 files changed, 8 insertions, 8 deletions
diff --git a/documentation/poky-ref-manual/usingpoky.xml b/documentation/poky-ref-manual/usingpoky.xml
index 2d2e3f6eac..2782e2b856 100644
--- a/documentation/poky-ref-manual/usingpoky.xml
+++ b/documentation/poky-ref-manual/usingpoky.xml
@@ -19,7 +19,7 @@
</para>
<para>
- Bitbake handles the parsing and execution of the data files.
+ BitBake handles the parsing and execution of the data files.
The data itself is of various types:
<itemizedlist>
<listitem><para>Recipes: Provides details about particular pieces of software</para></listitem>
@@ -31,7 +31,7 @@
</para>
<para>
- Bitbake knows how to combine multiple data sources together and refers to each data source
+ BitBake knows how to combine multiple data sources together and refers to each data source
as a <link linkend='usingpoky-changes-layers'>'layer'</link>.
</para>
@@ -43,10 +43,10 @@
</para>
<section id='usingpoky-components-bitbake'>
- <title>Bitbake</title>
+ <title>BitBake</title>
<para>
- Bitbake is the tool at the heart of Poky and is responsible
+ BitBake is the tool at the heart of Poky and is responsible
for parsing the metadata, generating a list of tasks from it
and then executing them. To see a list of the options BitBake
supports look at 'bitbake --help'.
@@ -63,13 +63,13 @@
$ bitbake matchbox-desktop
</literallayout>
Several different versions of <filename>matchbox-desktop</filename> might exist.
- Bitbake chooses the one selected by the distribution configuration.
+ BitBake chooses the one selected by the distribution configuration.
You can get more details about how BitBake chooses between different versions
and providers in the <link linkend='ref-bitbake-providers'>
'Preferences and Providers'</link> section.
</para>
<para>
- Bitbake also tries to execute any dependent tasks first.
+ BitBake also tries to execute any dependent tasks first.
So for example, before building <filename>matchbox-desktop</filename> BitBake
would build a cross compiler and glibc if they had not already been built.
</para>
@@ -241,7 +241,7 @@
<para>
This sequence first builds <filename>matchbox-desktop</filename> and then recompiles it.
The last command reruns all tasks, basically the packaging tasks, after the compile.
- Bitbake recognizes that the "compile" task was rerun and therefore understands that the other
+ BitBake recognizes that the "compile" task was rerun and therefore understands that the other
tasks also need to be run again.
</para>
@@ -270,7 +270,7 @@
</section>
<section id='usingpoky-debugging-bitbake'>
- <title>General Bitbake Problems</title>
+ <title>General BitBake Problems</title>
<para>
You can see debug output from BitBake by using the "-D" option.