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
27 lines
1.0 KiB
C++
27 lines
1.0 KiB
C++
//===- DependencyScanningService.cpp - clang-scan-deps service ------------===//
|
|
//
|
|
// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
|
|
// See https://llvm.org/LICENSE.txt for license information.
|
|
// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
|
|
//
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
#include "clang/Tooling/DependencyScanning/DependencyScanningService.h"
|
|
#include "llvm/Support/TargetSelect.h"
|
|
|
|
using namespace clang;
|
|
using namespace tooling;
|
|
using namespace dependencies;
|
|
|
|
DependencyScanningService::DependencyScanningService(
|
|
ScanningMode Mode, ScanningOutputFormat Format, bool ReuseFileManager,
|
|
bool SkipExcludedPPRanges)
|
|
: Mode(Mode), Format(Format), ReuseFileManager(ReuseFileManager),
|
|
SkipExcludedPPRanges(SkipExcludedPPRanges) {
|
|
// Initialize targets for object file support.
|
|
llvm::InitializeAllTargets();
|
|
llvm::InitializeAllTargetMCs();
|
|
llvm::InitializeAllAsmPrinters();
|
|
llvm::InitializeAllAsmParsers();
|
|
}
|