path: root/meta/conf/bitbake.conf
diff options
authorRichard Purdie <richard.purdie@linuxfoundation.org>2013-11-07 22:35:07 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-11-12 16:00:20 +0000
commitb7279f99639774674da806d37d252f388f33055f (patch)
tree2589e187ccdc32913035b8c68c69c4acabae4192 /meta/conf/bitbake.conf
parent22465cef87b4b1685b3b131751eaf528503b264c (diff)
bitbake.conf: Default DISTRO to nodistro
An empty distro value leads to OVERRIDES and FILESOVERRIDES containing "::" entries which causes odd issues such as files being included when they shouldn't be. We could put in anonymous python to guard against empty entries but its messy and setting a default value for DISTRO to something harmless is much easier. This patch adds a weak default and ensures the sanity test doesn't complain about it. DISTRO_VERSION and SDK_VERSION are also updated to match. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/conf/bitbake.conf')
1 files changed, 4 insertions, 0 deletions
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index d7b7a4b46f..ea313adca5 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -656,6 +656,10 @@ AUTO_LIBNAME_PKGS = "${PACKAGES}"
### Config file processing
+# An empty distro leads to :: entries in OVERRIDES and FILEOVERRIDES which
+# is a bad idea. Setting a dummy value is better than a ton of anonymous python.
+DISTRO ??= "nodistro"
# 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.