aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Bitcode/Writer/BitcodeWriter.cpp
diff options
context:
space:
mode:
authorAdrian Prantl <aprantl@apple.com>2020-03-19 18:51:36 -0700
committerAdrian Prantl <aprantl@apple.com>2020-04-06 15:51:30 -0700
commit1e05d7b3d3c6d29ff6f9493cc478a36244cc32bd (patch)
tree1609b9ccf80f3097d22ac71ec3528bc40bbd1910 /llvm/lib/Bitcode/Writer/BitcodeWriter.cpp
parent276d2b78ce4d9753ed9e46576b4c5ab27d0ebf45 (diff)
downloadllvm-1e05d7b3d3c6d29ff6f9493cc478a36244cc32bd.zip
llvm-1e05d7b3d3c6d29ff6f9493cc478a36244cc32bd.tar.gz
llvm-1e05d7b3d3c6d29ff6f9493cc478a36244cc32bd.tar.bz2
Remap the target (Xcode) SDK directory to the host SDK directory.
This is mostly useful for Swift support; it allows LLDB to substitute a matching SDK it shipped with instead of the sysroot path that was used at compile time. The goal of this is to make the Xcode SDK something that behaves more like the compiler's resource directory, as in that it ships with LLDB rather than with the debugged program. This important primarily for importing Swift and Clang modules in the expression evaluator, and getting at the APINotes from the SDK in Swift. For a cross-debugging scenario, this means you have to have an SDK for your target installed alongside LLDB. In Xcode this will always be the case. rdar://problem/60640017 Differential Revision: https://reviews.llvm.org/D76471
Diffstat (limited to 'llvm/lib/Bitcode/Writer/BitcodeWriter.cpp')
0 files changed, 0 insertions, 0 deletions