[oe-commits] Martin Jansa : bitbake.conf: Fix OVERRIDES description (After pb' s explanation)

[git version control]

Module: openembedded.git
Branch: shr/merge
Commit: 4afed71e299d2e5aa1bdde3a1401aae5918ef648
URL:    http://gitweb.openembedded.net/?p=openembedded.git&a=commit;h=4afed71e299d2e5aa1bdde3a1401aae5918ef648

Author: Martin Jansa <Martin.Jansa at gmail.com>
Date:   Thu Nov 19 14:38:19 2009 +0100

bitbake.conf: Fix OVERRIDES description (After pb's explanation)

---

 conf/bitbake.conf |   11 ++++++++---
 1 files changed, 8 insertions(+), 3 deletions(-)

diff --git a/conf/bitbake.conf b/conf/bitbake.conf
index 4435fdd..2f7cef2 100644
--- a/conf/bitbake.conf
+++ b/conf/bitbake.conf
@@ -651,10 +651,15 @@ BUILDCFG_NEEDEDVARS ?= "TARGET_ARCH TARGET_OS"
 ### Config file processing
 ###
 
+# Overrides are processed left to right, so the ones that are named later take precedence.
+# You generally want them to go from least to most specific.
+# 
 # This means that an envionment variable named '<foo>_arm' overrides an
-# environment variable '<foo>' (when ${TARGET_ARCH} is arm). And the same: an
-# environment variable '<foo>_ramses' overrides both '<foo>' and '<foo>_arm
-# when ${MACHINE} is 'ramses'. And finally '<foo>_local' overrides anything.
+# environment variable '<foo>' (when ${TARGET_ARCH} is arm).
+# an environment variable '<foo>_ramses' overrides '<foo>' but doesn't override
+# '<foo>_arm' when ${MACHINE} is 'ramses'. 
+# You can use combination ie you can use '<foo>_arm_ramses' to override both '<foo>' and '<foo>_arm'.
+# And finally '<foo>_local' overrides anything, but with lowest priority.
 #
 # This works for  functions as well, they are really just environment variables.
 # Default OVERRIDES to make compilation fail fast in case of build system misconfiguration.