forked from OSchip/llvm-project
de07b1e84d
When a project uses PCH with explicit modules, the build will look like this: 1. scan PCH dependencies 2. explicitly build PCH 3. scan TU dependencies 4. explicitly build TU Step 2 produces an object file for the PCH, which the dependency scanner needs to read in step 3. This patch adds support for this. The `clang-scan-deps` invocation in the attached test would fail without this change. Depends on D103516. Reviewed By: Bigcheese Differential Revision: https://reviews.llvm.org/D103519 |
||
|---|---|---|
| .. | ||
| ASTDiff | ||
| Core | ||
| DependencyScanning | ||
| DumpTool | ||
| Inclusions | ||
| Refactoring | ||
| Syntax | ||
| Transformer | ||
| AllTUsExecution.cpp | ||
| ArgumentsAdjusters.cpp | ||
| CMakeLists.txt | ||
| CommonOptionsParser.cpp | ||
| CompilationDatabase.cpp | ||
| EmptyNodeIntrospection.inc.in | ||
| Execution.cpp | ||
| ExpandResponseFilesCompilationDatabase.cpp | ||
| FileMatchTrie.cpp | ||
| FixIt.cpp | ||
| GuessTargetAndModeCompilationDatabase.cpp | ||
| InterpolatingCompilationDatabase.cpp | ||
| JSONCompilationDatabase.cpp | ||
| NodeIntrospection.cpp | ||
| Refactoring.cpp | ||
| RefactoringCallbacks.cpp | ||
| StandaloneExecution.cpp | ||
| Tooling.cpp | ||