Toolchains: Fall back to C compiler for output parser creation

Otherwise, there will be no output parser for toolchains that register
only a C compiler.

Change-Id: I3f3448ee85a0dc03701a6c9b21ec23b1d8ca2f22
Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
This commit is contained in:
Christian Kandeler
2019-02-07 15:20:58 +01:00
parent 9d25cb8720
commit 583e6ff5eb

View File

@@ -390,8 +390,11 @@ void ToolChainKitInformation::addToMacroExpander(Kit *kit, Utils::MacroExpander
IOutputParser *ToolChainKitInformation::createOutputParser(const Kit *k) const IOutputParser *ToolChainKitInformation::createOutputParser(const Kit *k) const
{ {
ToolChain *tc = toolChain(k, Constants::CXX_LANGUAGE_ID); for (const Core::Id langId : {Constants::CXX_LANGUAGE_ID, Constants::C_LANGUAGE_ID}) {
return tc ? tc->outputParser() : nullptr; if (const ToolChain * const tc = toolChain(k, langId))
return tc->outputParser();
}
return nullptr;
} }
QSet<Core::Id> ToolChainKitInformation::availableFeatures(const Kit *k) const QSet<Core::Id> ToolChainKitInformation::availableFeatures(const Kit *k) const