bitbake.conf: Define fallback DISTRO_NAME

When using OE-Core only we miss this define and its now used in recipes
like os-release, which goes undefined and when booting we see messages
like

Welcome to ${DISTRO_NAME} nodistro.0!

This would change to
Welcome to OpenEmbedded nodistro.0!

Remove all trailing whitespaces while touching this file

(From OE-Core rev: cf2383a63975ac7a51729a313fe0a52b559d2c61)

(From OE-Core rev: 394f0d61d1211a0562a3b4d9d78e8984abd3b28f)

Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Khem Raj
2015-08-22 19:38:55 -07:00
committed by Richard Purdie
parent 36e8f935a1
commit 06300055fa

View File

@@ -649,7 +649,7 @@ export PKG_CONFIG_DISABLE_UNINSTALLED = "yes"
# An empty distro leads to :: entries in OVERRIDES and FILEOVERRIDES which # 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. # is a bad idea. Setting a dummy value is better than a ton of anonymous python.
DISTRO ??= "nodistro" DISTRO ??= "nodistro"
DISTRO_NAME ??= "OpenEmbedded"
# Overrides are processed left to right, so the ones that are named later take precedence. # 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. # You generally want them to go from least to most specific.
# #