mirror of
git://git.yoctoproject.org/poky.git
synced 2025-07-19 12:59:02 +02:00
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... (From OE-Core rev: 1fd8882db9011a6fe18da7611fba3426fd5cb00d) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
0e6b9a1e5f
commit
f42b404a99
|
@ -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 '<foo>_arm' overrides a variable '<foo>' when ${TARGET_ARCH} is arm.
|
||||
# A variable '<foo>_qemuarm' overrides '<foo>' and overrides '<foo>_arm' when ${MACHINE} is 'qemuarm'.
|
||||
# If you use combination ie '<foo>_qemuarm_arm', then '<foo>_qemuarm_arm' will override
|
||||
# '<foo>_qemuarm' and then '<foo>' will be overriden with that value from '<foo>_qemuarm'.
|
||||
# And finally '<foo>_forcevariable' overrides any standard variable, with the highest priority.
|
||||
# A variable '<foo>:arm' overrides a variable '<foo>' when ${TARGET_ARCH} is arm.
|
||||
# A variable '<foo>:qemuarm' overrides '<foo>' and overrides '<foo>:arm' when ${MACHINE} is 'qemuarm'.
|
||||
# If you use combination ie '<foo>:qemuarm:arm', then '<foo>:qemuarm:arm' will override
|
||||
# '<foo>:qemuarm' and then '<foo>' will be overriden with that value from '<foo>:qemuarm'.
|
||||
# And finally '<foo>: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"
|
||||
|
|
Loading…
Reference in New Issue
Block a user