diff options
| author | Jonas Devlieghere <jonas@devlieghere.com> | 2025-03-19 22:22:01 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-03-19 22:22:01 -0700 |
| commit | 460c0f567cc83378d4aafd9fba95561bacf57fe4 (patch) | |
| tree | 06b73ab1b5afa18b9b6207e9b791db037ea98116 /llvm/lib/Target/RISCV/Disassembler/RISCVDisassembler.cpp | |
| parent | d99033e4b4081bc47510c451b618ef93fe2f3c62 (diff) | |
| download | llvm-460c0f567cc83378d4aafd9fba95561bacf57fe4.zip llvm-460c0f567cc83378d4aafd9fba95561bacf57fe4.tar.gz llvm-460c0f567cc83378d4aafd9fba95561bacf57fe4.tar.bz2 | |
[lldb] Move two methods from Platfrom -> Host (NFC) (#132119)
This moves two functions from Platform to Host:
1. GetCurrentXcodeToolchainDirectory
2. GetCurrentCommandLineToolsDirectory.
These two functions caused a layering violation in the Swift fork, which
added a dependency from lldbHost to lldbPlatform. As show by this PR,
there's no need for these two functions to live in Platform, and we
already have similar functions in Host.
We have various layering violations but this one is particularly bad,
because lldb-dap started depending on lldbHost. On the Swift fork, this
library was depending on lldbPlatform which pulled in various Swift
files, which libLLDB needs, but lldb-dap itself does not. We were
missing RPATHs to resume them, so in the current nightly, lldb-dap
crashes because the dynamic loader can't find the missing Swift libs.
rdar://146537366
Diffstat (limited to 'llvm/lib/Target/RISCV/Disassembler/RISCVDisassembler.cpp')
0 files changed, 0 insertions, 0 deletions