1
0
mirror of https://git.yoctoproject.org/poky synced 2026-06-02 01:19:52 +00:00

documentation/poky-ref-manual/usingpoky.xml: More BitBake changes

Forgot to search for "Bitbake" occurances.  These are now changed
to "BitBake."

(From OE-Core rev: 982826b61bf68244fad46ef52b5a203e648e330b)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2011-03-17 16:46:38 -06:00
committed by Richard Purdie
parent fa272d09b7
commit 2a144f85a9
+8 -8
View File
@@ -19,7 +19,7 @@
</para> </para>
<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: The data itself is of various types:
<itemizedlist> <itemizedlist>
<listitem><para>Recipes: Provides details about particular pieces of software</para></listitem> <listitem><para>Recipes: Provides details about particular pieces of software</para></listitem>
@@ -31,7 +31,7 @@
</para> </para>
<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>. as a <link linkend='usingpoky-changes-layers'>'layer'</link>.
</para> </para>
@@ -43,10 +43,10 @@
</para> </para>
<section id='usingpoky-components-bitbake'> <section id='usingpoky-components-bitbake'>
<title>Bitbake</title> <title>BitBake</title>
<para> <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 for parsing the metadata, generating a list of tasks from it
and then executing them. To see a list of the options BitBake and then executing them. To see a list of the options BitBake
supports look at 'bitbake --help'. supports look at 'bitbake --help'.
@@ -63,13 +63,13 @@
$ bitbake matchbox-desktop $ bitbake matchbox-desktop
</literallayout> </literallayout>
Several different versions of <filename>matchbox-desktop</filename> might exist. 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 You can get more details about how BitBake chooses between different versions
and providers in the <link linkend='ref-bitbake-providers'> and providers in the <link linkend='ref-bitbake-providers'>
'Preferences and Providers'</link> section. 'Preferences and Providers'</link> section.
</para> </para>
<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 So for example, before building <filename>matchbox-desktop</filename> BitBake
would build a cross compiler and glibc if they had not already been built. would build a cross compiler and glibc if they had not already been built.
</para> </para>
@@ -241,7 +241,7 @@
<para> <para>
This sequence first builds <filename>matchbox-desktop</filename> and then recompiles it. 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. 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. tasks also need to be run again.
</para> </para>
@@ -270,7 +270,7 @@
</section> </section>
<section id='usingpoky-debugging-bitbake'> <section id='usingpoky-debugging-bitbake'>
<title>General Bitbake Problems</title> <title>General BitBake Problems</title>
<para> <para>
You can see debug output from BitBake by using the "-D" option. You can see debug output from BitBake by using the "-D" option.