diff options
| author | Jan Svoboda <jan_svoboda@apple.com> | 2021-09-10 10:24:16 +0200 |
|---|---|---|
| committer | Jan Svoboda <jan_svoboda@apple.com> | 2021-09-10 11:02:41 +0200 |
| commit | 146ec74a8382dc820809d0a2bf4b918d0b5e6603 (patch) | |
| tree | bd51e23649b1d0ccbb9fdebfdcb011113763200d /lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationServerCommon.cpp | |
| parent | b25ab4f313f38d3dee9674789cf56b9143515034 (diff) | |
| download | llvm-146ec74a8382dc820809d0a2bf4b918d0b5e6603.zip llvm-146ec74a8382dc820809d0a2bf4b918d0b5e6603.tar.gz llvm-146ec74a8382dc820809d0a2bf4b918d0b5e6603.tar.bz2 | |
[clang][deps] NFC: Stop going through ClangTool
The dependency scanner currently uses `ClangTool` to invoke the dependency scanning action.
However, `ClangTool` seems to be the wrong level of abstraction. It's intended to be run over a collection of compile commands, which we actively avoid via `SingleCommandCompilationDatabase`. It automatically injects `-fsyntax-only` and other flags, which we avoid by calling `clearArgumentsAdjusters()`. It deduces the resource directory based on the current executable path, which we'd like to change to deducing from `argv[0]`.
Internally, `ClangTool` uses `ToolInvocation` which seems to be more in line with what the dependency scanner tries to achieve. This patch switches to directly using `ToolInvocation` instead. NFC.
Reviewed By: dexonsmith
Differential Revision: https://reviews.llvm.org/D108979
Diffstat (limited to 'lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationServerCommon.cpp')
0 files changed, 0 insertions, 0 deletions