[oe] [PATCH] bitbake.conf: Fix OVERRIDES description (After pb's explanation)
Martin Jansa
martin.jansa at gmail.com
Thu Nov 19 13:39:56 UTC 2009
---
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.
--
1.6.5.3
More information about the Openembedded-devel
mailing list