summaryrefslogtreecommitdiff
path: root/conf/bitbake.conf
diff options
context:
space:
mode:
authorMartin Jansa <Martin.Jansa@gmail.com>2009-11-19 20:18:55 +0100
committerMartin Jansa <Martin.Jansa@gmail.com>2009-11-19 20:19:43 +0100
commit70af4a882915cb51302734ca0de3b810f05df072 (patch)
tree847b5aa4a092925bdd239a4629d790663c4b91f5 /conf/bitbake.conf
parent5555bc82e576dfe4a58b5a0ccf0ee12aed8ad2aa (diff)
bitbake.conf: Fix OVERRIDES description (After pb's explanation)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Diffstat (limited to 'conf/bitbake.conf')
-rw-r--r--conf/bitbake.conf12
1 files changed, 9 insertions, 3 deletions
diff --git a/conf/bitbake.conf b/conf/bitbake.conf
index 4435fdd8bd..b69b6757db 100644
--- a/conf/bitbake.conf
+++ b/conf/bitbake.conf
@@ -651,10 +651,16 @@ 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'.
+# If you use combination ie '<foo>_arm_ramses', then '<foo>_arm_ramses' will override
+# '<foo>_arm' and then '<foo>' will be overriden with that value from '<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.