diff options
| -rw-r--r-- | bitbake/doc/manual/usermanual.xml | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/bitbake/doc/manual/usermanual.xml b/bitbake/doc/manual/usermanual.xml index 450ac77d7a..29cdf97a0a 100644 --- a/bitbake/doc/manual/usermanual.xml +++ b/bitbake/doc/manual/usermanual.xml | |||
| @@ -269,7 +269,9 @@ of the event and the content of the <varname>FILE</varname> variable.</para> | |||
| 269 | <title>Parsing</title> | 269 | <title>Parsing</title> |
| 270 | <section> | 270 | <section> |
| 271 | <title>Configuration Files</title> | 271 | <title>Configuration Files</title> |
| 272 | <para>The first of the classifications of metadata in BitBake is configuration metadata. This metadata is global, and therefore affects <emphasis>all</emphasis> packages and tasks which are executed. Currently, BitBake has hardcoded knowledge of a single configuration file. It expects to find 'conf/bitbake.conf' somewhere in the user specified <envar>BBPATH</envar>. That configuration file generally has include directives to pull in any other metadata (generally files specific to architecture, machine, <emphasis>local</emphasis> and so on.</para> | 272 | <para>The first of the classifications of metadata in BitBake is configuration metadata. This metadata is global, and therefore affects <emphasis>all</emphasis> packages and tasks which are executed.</para> |
| 273 | <papa>Bitbake will first search the current working directory for an optional "conf/bblayers.conf" configuration file. This file is expected to contain a BBLAYERS variable which is a space delimited list of 'layer' directories. For each directory in this list a "conf/layer.conf" file will be searched for and parsed with the LAYERDIR variable being set to the directory where the layer was found. The idea is these files will setup BBPATH and other variables correctly for a given build directory automatically for the user.</para> | ||
| 274 | <para>Bitbake will then expect to find 'conf/bitbake.conf' somewhere in the user specified <envar>BBPATH</envar>. That configuration file generally has include directives to pull in any other metadata (generally files specific to architecture, machine, <emphasis>local</emphasis> and so on.</para> | ||
| 273 | <para>Only variable definitions and include directives are allowed in .conf files.</para> | 275 | <para>Only variable definitions and include directives are allowed in .conf files.</para> |
| 274 | </section> | 276 | </section> |
| 275 | <section> | 277 | <section> |