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.xml36
1 files changed, 18 insertions, 18 deletions
diff --git a/documentation/poky-ref-manual/ref-bitbake.xml b/documentation/poky-ref-manual/ref-bitbake.xml
index d870387aa0..75b3bf5e54 100644
--- a/documentation/poky-ref-manual/ref-bitbake.xml
+++ b/documentation/poky-ref-manual/ref-bitbake.xml
@@ -33,15 +33,15 @@
33 33
34 <para> 34 <para>
35 The first thing BitBake does is look for the <filename>bitbake.conf</filename> file. 35 The first thing BitBake does is look for the <filename>bitbake.conf</filename> file.
36 Poky keeps this file in <filename class="directory">meta/conf/</filename>. 36 Poky keeps this file in <filename>meta/conf/</filename>.
37 BitBake finds it by examining the <filename>BBPATH</filename> environment 37 BitBake finds it by examining the <filename>BBPATH</filename> environment
38 variable and looking for the <filename class="directory">meta/conf/</filename> 38 variable and looking for the <filename>meta/conf/</filename>
39 directory. 39 directory.
40 </para> 40 </para>
41 41
42 <para> 42 <para>
43 In Poky, <filename>bitbake.conf</filename> lists other configuration 43 In Poky, <filename>bitbake.conf</filename> lists other configuration
44 files to include from a <filename class="directory">conf/</filename> 44 files to include from a <filename>conf/</filename>
45 directory below the directories listed in <filename>BBPATH</filename>. 45 directory below the directories listed in <filename>BBPATH</filename>.
46 In general the most important configuration file from a user's perspective 46 In general the most important configuration file from a user's perspective
47 is <filename>local.conf</filename>, which contains a user's customized 47 is <filename>local.conf</filename>, which contains a user's customized
@@ -54,11 +54,11 @@
54 The DISTRO and MACHINE environment variables are both usually set in 54 The DISTRO and MACHINE environment variables are both usually set in
55 the <filename>local.conf</filename> file. 55 the <filename>local.conf</filename> file.
56 Valid distribution 56 Valid distribution
57 configuration files are available in the <filename class="directory"> 57 configuration files are available in the <filename>
58 meta/conf/distro/</filename> directory and valid machine configuration 58 meta/conf/distro/</filename> directory and valid machine configuration
59 files in the <filename class="directory">meta/conf/machine/</filename> 59 files in the <filename>meta/conf/machine/</filename>
60 directory. 60 directory.
61 Within the <filename class="directory">meta/conf/machine/include/</filename> 61 Within the <filename>meta/conf/machine/include/</filename>
62 directory are various <filename>tune-*.inc</filename> configuration files that provide common 62 directory are various <filename>tune-*.inc</filename> configuration files that provide common
63 "tuning" settings specific to and shared between particular architectures and machines. 63 "tuning" settings specific to and shared between particular architectures and machines.
64 </para> 64 </para>
@@ -79,29 +79,29 @@
79 variable <glossterm><link linkend='var-BBFILES'>BBFILES</link></glossterm> 79 variable <glossterm><link linkend='var-BBFILES'>BBFILES</link></glossterm>
80 is set, usually in 80 is set, usually in
81 <filename>local.conf</filename>, and defines the list of places to search for 81 <filename>local.conf</filename>, and defines the list of places to search for
82 <filename class="extension">.bb</filename> files. 82 <filename>.bb</filename> files.
83 By default, the BBFILES variable specifies the <filename class="directory">meta/recipes-*/ 83 By default, the BBFILES variable specifies the <filename>meta/recipes-*/
84 </filename> directory within Poky. 84 </filename> directory within Poky.
85 Adding extra content to BBFILES is best achieved through the use of BitBake 85 Adding extra content to BBFILES is best achieved through the use of BitBake
86 <link linkend='usingpoky-changes-layers'>"layers"</link>. 86 <link linkend='usingpoky-changes-layers'>"layers"</link>.
87 </para> 87 </para>
88 88
89 <para> 89 <para>
90 BitBake parses each <filename class="extension">.bb</filename> file in BBFILES and 90 BitBake parses each <filename>.bb</filename> file in BBFILES and
91 stores the values of various variables. 91 stores the values of various variables.
92 In summary, for each <filename class="extension">.bb</filename> 92 In summary, for each <filename>.bb</filename>
93 file the configuration plus the base class of variables are set, followed 93 file the configuration plus the base class of variables are set, followed
94 by the data in the <filename class="extension">.bb</filename> file 94 by the data in the <filename>.bb</filename> file
95 itself, followed by any inherit commands that 95 itself, followed by any inherit commands that
96 <filename class="extension">.bb</filename> file might contain. 96 <filename>.bb</filename> file might contain.
97 </para> 97 </para>
98 98
99 <para> 99 <para>
100 Because parsing <filename class="extension">.bb</filename> files is a time 100 Because parsing <filename>.bb</filename> files is a time
101 consuming process, a cache is kept to speed up subsequent parsing. 101 consuming process, a cache is kept to speed up subsequent parsing.
102 This cache is invalid if the timestamp of the <filename class="extension">.bb</filename> 102 This cache is invalid if the timestamp of the <filename>.bb</filename>
103 file itself changes, or if the timestamps of any of the include, 103 file itself changes, or if the timestamps of any of the include,
104 configuration or class files the <filename class="extension">.bb</filename> 104 configuration or class files the <filename>.bb</filename>
105 file depends on changes. 105 file depends on changes.
106 </para> 106 </para>
107 </section> 107 </section>
@@ -110,7 +110,7 @@
110 <title>Preferences and Providers</title> 110 <title>Preferences and Providers</title>
111 111
112 <para> 112 <para>
113 Once all the <filename class="extension">.bb</filename> files have been 113 Once all the <filename>.bb</filename> files have been
114 parsed, BitBake starts to build the target (poky-image-sato in the previous section's 114 parsed, BitBake starts to build the target (poky-image-sato in the previous section's
115 example) and looks for providers of that target. 115 example) and looks for providers of that target.
116 Once a provider is selected, BitBake resolves all the dependencies for 116 Once a provider is selected, BitBake resolves all the dependencies for
@@ -200,11 +200,11 @@ PREFERRED_PROVIDER_virtual/kernel = "linux-rp"
200 <para> 200 <para>
201 As each task completes, a timestamp is written to the directory specified by the 201 As each task completes, a timestamp is written to the directory specified by the
202 <glossterm><link linkend='var-STAMPS'>STAMPS</link></glossterm> variable (usually 202 <glossterm><link linkend='var-STAMPS'>STAMPS</link></glossterm> variable (usually
203 <filename class="directory">build/tmp/stamps/*/</filename>). 203 <filename>build/tmp/stamps/*/</filename>).
204 On subsequent runs, BitBake looks at the STAMPS directory and does not rerun 204 On subsequent runs, BitBake looks at the STAMPS directory and does not rerun
205 tasks that are already completed unless a timestamp is found to be invalid. 205 tasks that are already completed unless a timestamp is found to be invalid.
206 Currently, invalid timestamps are only considered on a per 206 Currently, invalid timestamps are only considered on a per
207 <filename class="extension">.bb</filename> file basis. 207 <filename>.bb</filename> file basis.
208 So, for example, if the configure stamp has a timestamp greater than the 208 So, for example, if the configure stamp has a timestamp greater than the
209 compile timestamp for a given target then the compile task would rerun. 209 compile timestamp for a given target then the compile task would rerun.
210 Running the compile task again, however, has no effect on other providers 210 Running the compile task again, however, has no effect on other providers