aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/Serialization/ModuleFile.cpp
diff options
context:
space:
mode:
authornerix <nerixdev@outlook.de>2025-05-19 20:13:49 +0200
committerGitHub <noreply@github.com>2025-05-19 11:13:49 -0700
commit3bae8e2ef2ff02dcba745cb47ea1264fd08885cc (patch)
treeaae8b96299406e8df5503da44e65096a748eca72 /clang/lib/Serialization/ModuleFile.cpp
parent77de8a0c0abc9d245a7c6278670554b47ae183ea (diff)
downloadllvm-3bae8e2ef2ff02dcba745cb47ea1264fd08885cc.zip
llvm-3bae8e2ef2ff02dcba745cb47ea1264fd08885cc.tar.gz
llvm-3bae8e2ef2ff02dcba745cb47ea1264fd08885cc.tar.bz2
[lldb] Suppport testing with debug-python on Windows (#140443)
When trying to run the LLDB API tests on Windows with a debug configuration, they fail, because the `_lldb` module won't be found. As explained in https://github.com/llvm/llvm-project/issues/51272, this is because lit will run the test with `python.exe` but the module is built for the debug version of python, `python_d.exe`. CMake already resolved the debug executable in `Python3_EXECUTABLE_DEBUG`, so this PR changes the `config.python_executable` to point to `python_d.exe` on Windows in debug mode. The check is equivalent to the one done in the top-level LLDB CMakeLists [when setting the python suffix](https://github.com/llvm/llvm-project/blob/3ccb15d6caf57f2a866d496ada2fb52d14b179d2/lldb/CMakeLists.txt#L79-L86).
Diffstat (limited to 'clang/lib/Serialization/ModuleFile.cpp')
0 files changed, 0 insertions, 0 deletions