From: Peter Kjellerstedt Date: Thu, 26 Aug 2021 17:57:36 +0000 (+0200) Subject: bitbake.conf: Use the new variable override syntax in a comment X-Git-Tag: uninative-3.4~21 X-Git-Url: https://code.ossystems.io/gitweb?a=commitdiff_plain;h=1fd8882db9011a6fe18da7611fba3426fd5cb00d;p=openembedded-core.git bitbake.conf: Use the new variable override syntax in a comment It is probably a good idea if the comment that describes how variable overrides work use the new override syntax... Signed-off-by: Peter Kjellerstedt Signed-off-by: Richard Purdie --- diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf index 46c8d08620..2140d498f7 100644 --- a/meta/conf/bitbake.conf +++ b/meta/conf/bitbake.conf @@ -743,11 +743,11 @@ DISTRO_NAME ??= "OpenEmbedded" # 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: -# A variable '_arm' overrides a variable '' when ${TARGET_ARCH} is arm. -# A variable '_qemuarm' overrides '' and overrides '_arm' when ${MACHINE} is 'qemuarm'. -# If you use combination ie '_qemuarm_arm', then '_qemuarm_arm' will override -# '_qemuarm' and then '' will be overriden with that value from '_qemuarm'. -# And finally '_forcevariable' overrides any standard variable, with the highest priority. +# A variable ':arm' overrides a variable '' when ${TARGET_ARCH} is arm. +# A variable ':qemuarm' overrides '' and overrides ':arm' when ${MACHINE} is 'qemuarm'. +# If you use combination ie ':qemuarm:arm', then ':qemuarm:arm' will override +# ':qemuarm' and then '' will be overriden with that value from ':qemuarm'. +# And finally ':forcevariable' overrides any standard variable, with the highest priority. # This works for functions as well, they are really just variables. # OVERRIDES = "${TARGET_OS}:${TRANSLATED_TARGET_ARCH}:pn-${PN}:${MACHINEOVERRIDES}:${DISTROOVERRIDES}:${CLASSOVERRIDE}${LIBCOVERRIDE}:forcevariable"