[lldb-dev] help, how to get a debug build on windows (python37_d.lib)

[Ted Woodward via lldb-dev]

Hi Larry,

You can tell the Python installer to install the debug libraries.

I recently switch from VS 2015 to VS 2017 to build LLDB. My debug builds stopped working – it couldn’t link with the Python debug library, even though I had it in the right place. My guess is the Python I’m using (3.5.1) was built with 2015, and the 2017 linker didn’t like linking against the debug library built with 2015.

I switched from a Debug build to RelWithDebInfo, and it worked.

Ted

From: lldb-dev <lldb-dev-bounces at lists.llvm.org> On Behalf Of Larry D'Anna via lldb-dev
Sent: Sunday, September 22, 2019 1:21 PM
To: lldb-dev at lists.llvm.org
Subject: [EXT] [lldb-dev] help, how to get a debug build on windows (python37_d.lib)

Hi lldb-dev.

I can’t seem to figure out how to build a debug lldb on windows.   It wants to link against a debug version of Python, which isn’t there.

My cmake line looks like this:

cmake -G Ninja `
        "-DPYTHON_HOME=C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64" `
        "-DLLVM_ENABLE_PROJECTS=clang;lldb;libcxx;libcxxabi;lld" `
     "-DSWIG_EXECUTABLE=C:\ProgramData\chocolatey\bin\swig.exe" `
        "C:\Users\smoofra\llvm-project\llvm"
I also made this change, to tell it to link against the release python.

--- a/lldb/cmake/modules/LLDBConfig.cmake
+++ b/lldb/cmake/modules/LLDBConfig.cmake
@@ -227,7 +227,7 @@ function(find_python_libs_windows)
   else()
     # Lookup for concrete python installation depending on build type
     if (CMAKE_BUILD_TYPE STREQUAL Debug)
-      set(LOOKUP_DEBUG_PYTHON TRUE)
+      set(LOOKUP_DEBUG_PYTHON FALSE)
     else()
       set(LOOKUP_DEBUG_PYTHON FALSE)
     endif()
But somehow at the very end, the link still fails because python37_d.lib isn’t there.

Anybody know what I’m doing wrong?  Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20190923/b9b54959/attachment-0001.html>