clang-tools 22.0.0git
|
Public Member Functions | |
ModulesBuilderImpl (const GlobalCompilationDatabase &CDB) | |
ModuleNameToSourceCache & | getProjectModulesCache () |
const GlobalCompilationDatabase & | getCDB () const |
llvm::Error | getOrBuildModuleFile (PathRef RequiredSource, StringRef ModuleName, const ThreadsafeFS &TFS, CachingProjectModules &MDB, ReusablePrerequisiteModules &BuiltModuleFiles) |
Definition at line 537 of file ModulesBuilder.cpp.
|
inline |
Definition at line 539 of file ModulesBuilder.cpp.
|
inline |
Definition at line 544 of file ModulesBuilder.cpp.
Referenced by getOrBuildModuleFile().
llvm::Error clang::clangd::ModulesBuilder::ModulesBuilderImpl::getOrBuildModuleFile | ( | PathRef | RequiredSource, |
StringRef | ModuleName, | ||
const ThreadsafeFS & | TFS, | ||
CachingProjectModules & | MDB, | ||
ReusablePrerequisiteModules & | BuiltModuleFiles ) |
It is possible that we're meeting third party modules (modules whose source are not in the project. e.g, the std module may be a third-party module for most project) or something wrong with the implementation of ProjectModules. FIXME: How should we treat third party modules here? If we want to ignore third party modules, we should return true instead of false here. Currently we simply bail out.
Try to get prebuilt module files from the compilation database first. This helps to avoid building the module files that are already built by the compiler.
Definition at line 597 of file ModulesBuilder.cpp.
References getCDB(), clang::clangd::log(), and clang::clangd::ThreadsafeFS::view().
|
inline |
Definition at line 541 of file ModulesBuilder.cpp.