From cefeeb1aa30a9d8744a6ff9c51811ebc8d18c735 Mon Sep 17 00:00:00 2001 From: Richard Purdie Date: Mon, 22 Mar 2010 17:58:27 +0000 Subject: usermanual.xml: Add documentation on bblayers.conf (Bitbake rev: 879229d12c2830dba9e0cb794e61e3c698b8dcc7) Signed-off-by: Richard Purdie --- bitbake/doc/manual/usermanual.xml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) 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 FILE variable. Parsing
Configuration Files - The first of the classifications of metadata in BitBake is configuration metadata. This metadata is global, and therefore affects all 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 BBPATH. That configuration file generally has include directives to pull in any other metadata (generally files specific to architecture, machine, local and so on. + The first of the classifications of metadata in BitBake is configuration metadata. This metadata is global, and therefore affects all packages and tasks which are executed. + 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. + Bitbake will then expect to find 'conf/bitbake.conf' somewhere in the user specified BBPATH. That configuration file generally has include directives to pull in any other metadata (generally files specific to architecture, machine, local and so on. Only variable definitions and include directives are allowed in .conf files.
-- cgit v1.2.3-54-g00ecf