diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2012-06-13 09:23:12 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2012-06-29 14:59:22 +0100 |
commit | 4b72728755b7c4d947c6dd352b190653f7fbb3f8 (patch) | |
tree | cc80afc785fd494a62ce2b2407b5bbdf10ee9b2c /documentation/poky-ref-manual/ref-bitbake.xml | |
parent | 1cc3056b3ac8f11c800e0bf8874a26e491fc3ae9 (diff) | |
download | poky-4b72728755b7c4d947c6dd352b190653f7fbb3f8.tar.gz |
documentation/poky-ref-manual/ref-bitbake.xml: 1.1.2 variables and updates
First pass at implementing the poky.ent variables. Made some obvious
typo corrections as well.
(From yocto-docs rev: 4773e7703d88456b272c13dc197c94bd7b09d59e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/poky-ref-manual/ref-bitbake.xml')
-rw-r--r-- | documentation/poky-ref-manual/ref-bitbake.xml | 24 |
1 files changed, 12 insertions, 12 deletions
diff --git a/documentation/poky-ref-manual/ref-bitbake.xml b/documentation/poky-ref-manual/ref-bitbake.xml index fa6bc70e55..8f0023cf1d 100644 --- a/documentation/poky-ref-manual/ref-bitbake.xml +++ b/documentation/poky-ref-manual/ref-bitbake.xml | |||
@@ -1,5 +1,6 @@ | |||
1 | <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" | 1 | <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" |
2 | "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> | 2 | "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" |
3 | [<!ENTITY % poky SYSTEM "../poky.ent"> %poky; ] > | ||
3 | 4 | ||
4 | <appendix id='ref-bitbake'> | 5 | <appendix id='ref-bitbake'> |
5 | 6 | ||
@@ -35,7 +36,7 @@ | |||
35 | The first thing BitBake does is look for the <filename>bitbake.conf</filename> file. | 36 | The first thing BitBake does is look for the <filename>bitbake.conf</filename> file. |
36 | The Yocto Project keeps this file in the Yocto Project file's <filename>meta/conf/</filename> | 37 | The Yocto Project keeps this file in the Yocto Project file's <filename>meta/conf/</filename> |
37 | directory. | 38 | directory. |
38 | BitBake finds it by examining the <filename>BBPATH</filename> environment | 39 | BitBake finds it by examining its <filename>BBPATH</filename> environment |
39 | variable and looking for the <filename>meta/conf/</filename> | 40 | variable and looking for the <filename>meta/conf/</filename> |
40 | directory. | 41 | directory. |
41 | </para> | 42 | </para> |
@@ -53,7 +54,7 @@ | |||
53 | and the machine configuration file | 54 | and the machine configuration file |
54 | (set by the | 55 | (set by the |
55 | <filename><link linkend='var-MACHINE'>MACHINE</link></filename> variable). | 56 | <filename><link linkend='var-MACHINE'>MACHINE</link></filename> variable). |
56 | The <filename>DISTRO</filename> and <filename>MACHINE</filename> environment | 57 | The <filename>DISTRO</filename> and <filename>MACHINE</filename> BitBake environment |
57 | variables are both usually set in | 58 | variables are both usually set in |
58 | the <filename>local.conf</filename> file. | 59 | the <filename>local.conf</filename> file. |
59 | Valid distribution | 60 | Valid distribution |
@@ -86,7 +87,7 @@ | |||
86 | <filename>meta/recipes-*/</filename> directory within Poky. | 87 | <filename>meta/recipes-*/</filename> directory within Poky. |
87 | Adding extra content to <filename>BBFILES</filename> is best achieved through the use of | 88 | Adding extra content to <filename>BBFILES</filename> is best achieved through the use of |
88 | BitBake layers as described in the | 89 | BitBake layers as described in the |
89 | <link linkend='usingpoky-changes-layers'>BitBake Layers</link> section. | 90 | "<link linkend='usingpoky-changes-layers'>BitBake Layers</link>" section. |
90 | </para> | 91 | </para> |
91 | 92 | ||
92 | <para> | 93 | <para> |
@@ -207,17 +208,16 @@ | |||
207 | It is worth noting that you can greatly speed up the build time by properly setting | 208 | It is worth noting that you can greatly speed up the build time by properly setting |
208 | the <filename>BB_NUMBER_THREADS</filename> variable. | 209 | the <filename>BB_NUMBER_THREADS</filename> variable. |
209 | See the | 210 | See the |
210 | <ulink url='http://www.yoctoproject.org/docs/1.1.1/yocto-project-qs/yocto-project-qs.html#building-image'> | 211 | "<ulink url='&YOCTO_DOCS_QS_URL;#building-image'>Building an Image</ulink>" |
211 | Building an Image</ulink> section in the | 212 | section in the Yocto Project Quick Start for more information. |
212 | <ulink url='http://www.yoctoproject.org/docs/1.1.1/yocto-project-qs/yocto-project-qs.html'> | ||
213 | Yocto Project Quick Start</ulink> for more information. | ||
214 | </para> | 213 | </para> |
215 | 214 | ||
216 | <para> | 215 | <para> |
217 | As each task completes, a timestamp is written to the directory specified by the | 216 | As each task completes, a timestamp is written to the directory specified by the |
218 | <filename><link linkend='var-STAMPS'>STAMPS</link></filename> variable (usually | 217 | <filename><link linkend='var-STAMPS'>STAMPS</link></filename> variable (usually |
219 | <filename>build/tmp/stamps/*/</filename>). | 218 | <filename>build/tmp/stamps/*/</filename>). |
220 | On subsequent runs, BitBake looks at the <filename>STAMPS</filename> directory and does not rerun | 219 | On subsequent runs, BitBake looks at the <filename>/build/tmp/stamps</filename> |
220 | directory and does not rerun | ||
221 | tasks that are already completed unless a timestamp is found to be invalid. | 221 | tasks that are already completed unless a timestamp is found to be invalid. |
222 | Currently, invalid timestamps are only considered on a per | 222 | Currently, invalid timestamps are only considered on a per |
223 | <filename>.bb</filename> file basis. | 223 | <filename>.bb</filename> file basis. |
@@ -301,7 +301,7 @@ | |||
301 | variable so that the shared state code ignores the dependency when it creates | 301 | variable so that the shared state code ignores the dependency when it creates |
302 | checksums. | 302 | checksums. |
303 | For information on this process, see the <filename>BB_HASHBASE_WHITELIST</filename> | 303 | For information on this process, see the <filename>BB_HASHBASE_WHITELIST</filename> |
304 | example in <xref linkend='checksums'>Checksums (Signatures)</xref>. | 304 | example in the "<link linkend='checksums'>Checksums (Signatures)</link>" section. |
305 | </note> | 305 | </note> |
306 | </section> | 306 | </section> |
307 | 307 | ||
@@ -401,8 +401,8 @@ Options: | |||
401 | This feature works using the <filename><link linkend='var-SRCREV'>SRCREV</link></filename> | 401 | This feature works using the <filename><link linkend='var-SRCREV'>SRCREV</link></filename> |
402 | variable. | 402 | variable. |
403 | See the | 403 | See the |
404 | <link linkend='platdev-appdev-srcrev'>Development Within Yocto Project for a Package that Uses | 404 | "<link linkend='platdev-appdev-srcrev'>Development Within Yocto Project for a Package that Uses |
405 | an External SCM</link> section for more information. | 405 | an External SCM</link>" section for more information. |
406 | </para> | 406 | </para> |
407 | 407 | ||
408 | </section> | 408 | </section> |