summaryrefslogtreecommitdiffstats
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:10 +0000
commit5066fbcfb4ef146ed800b1ef0dd6eaf938fd0d90 (patch)
tree00ad8df3248e7b1f3224e01cf0870dd614903b0d
parentad6b2f2e0bad0d7556f1fb041c5fe6d15972e25b (diff)
downloadpoky-5066fbcfb4ef146ed800b1ef0dd6eaf938fd0d90.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: 260e7dea7879846bcd3f3475cef001e512c657f0) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-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 b0bfae5ba5..8d4aafd464 100644
--- a/documentation/ref-manual/closer-look.xml
+++ b/documentation/ref-manual/closer-look.xml
@@ -255,9 +255,24 @@
255 255
256 <para> 256 <para>
257 When you launch your build with the 257 When you launch your build with the
258 <filename>bitbake <replaceable>target</replaceable></filename> command, BitBake 258 <filename>bitbake <replaceable>target</replaceable></filename>
259 sorts out the configurations to ultimately define your build 259 command, BitBake sorts out the configurations to ultimately
260 environment. 260 define your build environment.
261 It is important to understand that the OpenEmbedded build system
262 reads the configuration files in a specific order:
263 <filename>site.conf</filename>, <filename>auto.conf</filename>,
264 and <filename>local.conf</filename>.
265 And, the build system applies the normal assignment statement
266 rules.
267 Because the files are parsed in a specific order, variable
268 assignments for the same variable could be affected.
269 For example, if the <filename>auto.conf</filename> file and
270 the <filename>local.conf</filename> set
271 <replaceable>variable1</replaceable> to different values, because
272 the build system parses <filename>local.conf</filename> after
273 <filename>auto.conf</filename>,
274 <replaceable>variable1</replaceable> is assigned the value from
275 the <filename>local.conf</filename> file.
261 </para> 276 </para>
262 </section> 277 </section>
263 278