forked from qt-creator/qt-creator
Do not set up the "clang" binary as a C++ compiler
"clang" behaves differently than "clang++", even if it is the same file. In particular, "clang" will not properly act as a linker for C++ projects. Change-Id: I1654ccec0755c9b4534cc2be06de03c5d6bc42d2 Reviewed-by: hjk <hjk@qt.io>
This commit is contained in:
@@ -1449,9 +1449,6 @@ QList<ToolChain *> ClangToolChainFactory::autoDetect(const QList<ToolChain *> &a
|
|||||||
if (!compilerPath.isEmpty()) {
|
if (!compilerPath.isEmpty()) {
|
||||||
const FileName clang = compilerPath.parentDir().appendPath(
|
const FileName clang = compilerPath.parentDir().appendPath(
|
||||||
HostOsInfo::withExecutableSuffix("clang"));
|
HostOsInfo::withExecutableSuffix("clang"));
|
||||||
tcs.append(autoDetectToolchains(clang,
|
|
||||||
hostAbi, Constants::CXX_LANGUAGE_ID,
|
|
||||||
Constants::CLANG_TOOLCHAIN_TYPEID, alreadyKnown));
|
|
||||||
tcs.append(autoDetectToolchains(clang,
|
tcs.append(autoDetectToolchains(clang,
|
||||||
hostAbi, Constants::C_LANGUAGE_ID,
|
hostAbi, Constants::C_LANGUAGE_ID,
|
||||||
Constants::CLANG_TOOLCHAIN_TYPEID, alreadyKnown));
|
Constants::CLANG_TOOLCHAIN_TYPEID, alreadyKnown));
|
||||||
|
Reference in New Issue
Block a user