summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorScott Rifenbark <srifenbark@gmail.com>2016-02-15 08:26:50 -0800
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-03-03 17:40:19 +0000
commita4398c7ff7b0cc7bbbc904f1bd09d619ab6c401f (patch)
treeb1d3cecc729ba716aaed9fe9cd37a97bf44979ba /documentation
parent05c31507da0f046bc9fb113ddb0c69089ffa5c4e (diff)
downloadpoky-a4398c7ff7b0cc7bbbc904f1bd09d619ab6c401f.tar.gz
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: ce3f2344550ae1b735082d10f4f17ff555d24c38) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
-rw-r--r--documentation/ref-manual/closer-look.xml21
1 files changed, 18 insertions, 3 deletions
diff --git a/documentation/ref-manual/closer-look.xml b/documentation/ref-manual/closer-look.xml
index 45dcd9b3cf..4c5308e499 100644
--- a/documentation/ref-manual/closer-look.xml
+++ b/documentation/ref-manual/closer-look.xml
@@ -254,9 +254,24 @@
254 254
255 <para> 255 <para>
256 When you launch your build with the 256 When you launch your build with the
257 <filename>bitbake <replaceable>target</replaceable></filename> command, BitBake 257 <filename>bitbake <replaceable>target</replaceable></filename>
258 sorts out the configurations to ultimately define your build 258 command, BitBake sorts out the configurations to ultimately
259 environment. 259 define your build environment.
260 It is important to understand that the OpenEmbedded build system
261 reads the configuration files in a specific order:
262 <filename>site.conf</filename>, <filename>auto.conf</filename>,
263 and <filename>local.conf</filename>.
264 And, the build system applies the normal assignment statement
265 rules.
266 Because the files are parsed in a specific order, variable
267 assignments for the same variable could be affected.
268 For example, if the <filename>auto.conf</filename> file and
269 the <filename>local.conf</filename> set
270 <replaceable>variable1</replaceable> to different values, because
271 the build system parses <filename>local.conf</filename> after
272 <filename>auto.conf</filename>,
273 <replaceable>variable1</replaceable> is assigned the value from
274 the <filename>local.conf</filename> file.
260 </para> 275 </para>
261 </section> 276 </section>
262 277