diff options
author | Jonas Devlieghere <jonas@devlieghere.com> | 2024-06-17 14:52:40 -0700 |
---|---|---|
committer | Jonas Devlieghere <jonas@devlieghere.com> | 2024-06-17 15:15:28 -0700 |
commit | 0041582b6ca137ad04e26985a87a1ae45fb0f0bb (patch) | |
tree | c16ff1cb6798ba168df0ab3468072cb4ae855dba /llvm/lib/Analysis/ModuleSummaryAnalysis.cpp | |
parent | 68fc8dffe4669fed1f7eb88e6770509505f9960a (diff) | |
download | llvm-0041582b6ca137ad04e26985a87a1ae45fb0f0bb.zip llvm-0041582b6ca137ad04e26985a87a1ae45fb0f0bb.tar.gz llvm-0041582b6ca137ad04e26985a87a1ae45fb0f0bb.tar.bz2 |
[lldb] Fix Python interpreter workaround (attempt #2)
On macOS, to make DYLD_INSERT_LIBRARIES and the Python shim work
together, we have a workaroud that copies the "real" Python interpreter
into the build directory. This doesn't work when running in a virtual
environment, as the copied interpreter cannot find the packages
installed in the virtual environment relative to itself.
Address this issue by copying the Python interpreter into the virtual
environment's `bin` folder, rather than the build folder, when the test
suite detects that it's being run inside a virtual environment.
I'm not thrilled about this solution because it puts a file outside the
build directory. However, given virtual environments are considered
disposable, this seems reasonable.
Diffstat (limited to 'llvm/lib/Analysis/ModuleSummaryAnalysis.cpp')
0 files changed, 0 insertions, 0 deletions