diff options
| -rw-r--r-- | documentation/poky-ref-manual/usingpoky.xml | 16 |
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 @@ | |||
| 19 | </para> | 19 | </para> |
| 20 | 20 | ||
| 21 | <para> | 21 | <para> |
| 22 | Bitbake handles the parsing and execution of the data files. | 22 | BitBake handles the parsing and execution of the data files. |
| 23 | The data itself is of various types: | 23 | The data itself is of various types: |
| 24 | <itemizedlist> | 24 | <itemizedlist> |
| 25 | <listitem><para>Recipes: Provides details about particular pieces of software</para></listitem> | 25 | <listitem><para>Recipes: Provides details about particular pieces of software</para></listitem> |
| @@ -31,7 +31,7 @@ | |||
| 31 | </para> | 31 | </para> |
| 32 | 32 | ||
| 33 | <para> | 33 | <para> |
| 34 | Bitbake knows how to combine multiple data sources together and refers to each data source | 34 | BitBake knows how to combine multiple data sources together and refers to each data source |
| 35 | as a <link linkend='usingpoky-changes-layers'>'layer'</link>. | 35 | as a <link linkend='usingpoky-changes-layers'>'layer'</link>. |
| 36 | </para> | 36 | </para> |
| 37 | 37 | ||
| @@ -43,10 +43,10 @@ | |||
| 43 | </para> | 43 | </para> |
| 44 | 44 | ||
| 45 | <section id='usingpoky-components-bitbake'> | 45 | <section id='usingpoky-components-bitbake'> |
| 46 | <title>Bitbake</title> | 46 | <title>BitBake</title> |
| 47 | 47 | ||
| 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'. |
| @@ -63,13 +63,13 @@ | |||
| 63 | $ bitbake matchbox-desktop | 63 | $ bitbake matchbox-desktop |
| 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> |
| @@ -241,7 +241,7 @@ | |||
| 241 | <para> | 241 | <para> |
| 242 | This sequence first builds <filename>matchbox-desktop</filename> and then recompiles it. | 242 | This sequence first builds <filename>matchbox-desktop</filename> and then recompiles it. |
| 243 | The last command reruns all tasks, basically the packaging tasks, after the compile. | 243 | The last command reruns all tasks, basically the packaging tasks, after the compile. |
| 244 | Bitbake recognizes that the "compile" task was rerun and therefore understands that the other | 244 | BitBake recognizes that the "compile" task was rerun and therefore understands that the other |
| 245 | tasks also need to be run again. | 245 | tasks also need to be run again. |
| 246 | </para> | 246 | </para> |
| 247 | 247 | ||
| @@ -270,7 +270,7 @@ | |||
| 270 | </section> | 270 | </section> |
| 271 | 271 | ||
| 272 | <section id='usingpoky-debugging-bitbake'> | 272 | <section id='usingpoky-debugging-bitbake'> |
| 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. |
