From 5066fbcfb4ef146ed800b1ef0dd6eaf938fd0d90 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Mon, 15 Feb 2016 08:26:50 -0800 Subject: ref-manual: Added order information for conf file parsing. I included a new paragraph at the end of the section describing configuration in the "Closer Look" chapter. Cases exist when two configuration files set the same variable. Depending on the order, the last configuration file parsed is the one that actually sets the variable. Fixes [YOCTO #8914] (From yocto-docs rev: 260e7dea7879846bcd3f3475cef001e512c657f0) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/ref-manual/closer-look.xml | 21 ++++++++++++++++++--- 1 file changed, 18 insertions(+), 3 deletions(-) (limited to 'documentation/ref-manual/closer-look.xml') diff --git a/documentation/ref-manual/closer-look.xml b/documentation/ref-manual/closer-look.xml index b0bfae5ba5..8d4aafd464 100644 --- a/documentation/ref-manual/closer-look.xml +++ b/documentation/ref-manual/closer-look.xml @@ -255,9 +255,24 @@ When you launch your build with the - bitbake target command, BitBake - sorts out the configurations to ultimately define your build - environment. + bitbake target + command, BitBake sorts out the configurations to ultimately + define your build environment. + It is important to understand that the OpenEmbedded build system + reads the configuration files in a specific order: + site.conf, auto.conf, + and local.conf. + And, the build system applies the normal assignment statement + rules. + Because the files are parsed in a specific order, variable + assignments for the same variable could be affected. + For example, if the auto.conf file and + the local.conf set + variable1 to different values, because + the build system parses local.conf after + auto.conf, + variable1 is assigned the value from + the local.conf file. -- cgit v1.2.3-54-g00ecf