diff options
author | Andre McCurdy <armccurdy@gmail.com> | 2018-05-14 17:18:22 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2018-05-22 13:13:33 +0100 |
commit | 83174004509c511ec93a0bc405ff0e55964f2291 (patch) | |
tree | 8c268c565bca093fb8017cf66d816e0f7f3ec0be /meta/conf/bitbake.conf | |
parent | fc57f9cce3a4f4eb81ddd8b598443ce65fb0972b (diff) | |
download | poky-83174004509c511ec93a0bc405ff0e55964f2291.tar.gz |
bitbake.conf: drop obsolete comment referring to the fail-fast over-ride
The comment appears to have been accidentally left behind when the
fail-fast over-ride was removed by:
http://git.openembedded.org/openembedded-core/commit/?id=83ce96f44516c8a4a44c8c0140949256f8422014
Also update comments to refer to bitbake variables as just variables,
rather than environment variables.
(From OE-Core rev: 819935bba9047ad8af63bd5d1c199fecf96572b2)
Signed-off-by: Andre McCurdy <armccurdy@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/conf/bitbake.conf')
-rw-r--r-- | meta/conf/bitbake.conf | 13 |
1 files changed, 5 insertions, 8 deletions
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf index 702f498fef..6ecf78b078 100644 --- a/meta/conf/bitbake.conf +++ b/meta/conf/bitbake.conf | |||
@@ -722,19 +722,16 @@ export PKG_CONFIG_SYSTEM_INCLUDE_PATH = "${includedir}" | |||
722 | # is a bad idea. Setting a dummy value is better than a ton of anonymous python. | 722 | # is a bad idea. Setting a dummy value is better than a ton of anonymous python. |
723 | DISTRO ??= "nodistro" | 723 | DISTRO ??= "nodistro" |
724 | DISTRO_NAME ??= "OpenEmbedded" | 724 | DISTRO_NAME ??= "OpenEmbedded" |
725 | |||
725 | # Overrides are processed left to right, so the ones that are named later take precedence. | 726 | # Overrides are processed left to right, so the ones that are named later take precedence. |
726 | # You generally want them to go from least to most specific. | 727 | # You generally want them to go from least to most specific. This means that: |
727 | # | 728 | # A variable '<foo>_arm' overrides a variable '<foo>' when ${TARGET_ARCH} is arm. |
728 | # This means that an envionment variable named '<foo>_arm' overrides an | 729 | # A variable '<foo>_qemuarm' overrides '<foo>' and overrides '<foo>_arm' when ${MACHINE} is 'qemuarm'. |
729 | # environment variable '<foo>' (when ${TARGET_ARCH} is arm). | ||
730 | # An environment variable '<foo>_qemuarm' overrides '<foo>' and overrides | ||
731 | # '<foo>_arm' when ${MACHINE} is 'qemuarm'. | ||
732 | # If you use combination ie '<foo>_qemuarm_arm', then '<foo>_qemuarm_arm' will override | 730 | # If you use combination ie '<foo>_qemuarm_arm', then '<foo>_qemuarm_arm' will override |
733 | # '<foo>_qemuarm' and then '<foo>' will be overriden with that value from '<foo>_qemuarm'. | 731 | # '<foo>_qemuarm' and then '<foo>' will be overriden with that value from '<foo>_qemuarm'. |
734 | # And finally '<foo>_forcevariable' overrides any standard variable, with the highest priority. | 732 | # And finally '<foo>_forcevariable' overrides any standard variable, with the highest priority. |
733 | # This works for functions as well, they are really just variables. | ||
735 | # | 734 | # |
736 | # This works for functions as well, they are really just environment variables. | ||
737 | # Default OVERRIDES to make compilation fail fast in case of build system misconfiguration. | ||
738 | OVERRIDES = "${TARGET_OS}:${TRANSLATED_TARGET_ARCH}:pn-${PN}:${MACHINEOVERRIDES}:${DISTROOVERRIDES}:${CLASSOVERRIDE}${LIBCOVERRIDE}:forcevariable" | 735 | OVERRIDES = "${TARGET_OS}:${TRANSLATED_TARGET_ARCH}:pn-${PN}:${MACHINEOVERRIDES}:${DISTROOVERRIDES}:${CLASSOVERRIDE}${LIBCOVERRIDE}:forcevariable" |
739 | LIBCOVERRIDE ?= "" | 736 | LIBCOVERRIDE ?= "" |
740 | CLASSOVERRIDE ?= "class-target" | 737 | CLASSOVERRIDE ?= "class-target" |