forked from qt-creator/qt-creator
ClangTools: Always use CompilerOptionsBuilder for clang tools
We do not ship clang-cl anymore which makes it impossible to run clang with MSVC options. Secondly we used to we tweak compiler options quite a bit so why not to switch to CompilerOptionsBuilder totally? Change-Id: Id323cb554587afaea7d9aa530e947a45a03922d1 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
This commit is contained in:
@@ -1101,19 +1101,6 @@ QFuture<void> CppModelManager::updateProjectInfo(QFutureInterface<void> &futureI
|
||||
return indexingFuture;
|
||||
}
|
||||
|
||||
ProjectInfo CppModelManager::updateCompilerCallDataForProject(
|
||||
ProjectExplorer::Project *project,
|
||||
ProjectInfo::CompilerCallData &compilerCallData)
|
||||
{
|
||||
QMutexLocker locker(&d->m_projectMutex);
|
||||
|
||||
ProjectInfo projectInfo = d->m_projectToProjectsInfo.value(project, ProjectInfo());
|
||||
projectInfo.setCompilerCallData(compilerCallData);
|
||||
d->m_projectToProjectsInfo.insert(project, projectInfo);
|
||||
|
||||
return projectInfo;
|
||||
}
|
||||
|
||||
ProjectPart::Ptr CppModelManager::projectPartForId(const QString &projectPartId) const
|
||||
{
|
||||
return d->m_projectPartIdToProjectProjectPart.value(projectPartId);
|
||||
|
Reference in New Issue
Block a user