[all-commits] [llvm/llvm-project] 93d326: [lldb] [cmake] Fix delayloading liblldb.dll in min...
Martin Storsjö via All-commits
all-commits at lists.llvm.org
Fri Oct 10 08:18:35 PDT 2025
Branch: refs/heads/main
Home: https://github.com/llvm/llvm-project
Commit: 93d326038959fd87fb666a8bf97d774d0abb3591
https://github.com/llvm/llvm-project/commit/93d326038959fd87fb666a8bf97d774d0abb3591
Author: Martin Storsjö <martin at martin.st>
Date: 2025-10-10 (Fri, 10 Oct 2025)
Changed paths:
M lldb/cmake/modules/AddLLDB.cmake
Log Message:
-----------
[lldb] [cmake] Fix delayloading liblldb.dll in mingw builds (#162831)
ec28b95b7491bc2fbb6ec66cdbfd939e71255c42 made liblldb delayloaded, but
the supplied command line parameter is only valid for MSVC style builds.
For mingw builds using LLD, we can easily pass a similar option. For
mingw builds with ld.bfd, we can't quite as easily delayload it - for
these cases, just keep linking it like we usually do, and warn if the
user tried to set LLDB_PYTHON_DLL_RELATIVE_PATH in a build where it
won't have any effect.
Also change the setting for MSVC style builds, to use the simpler
`$<TARGET_FILE_NAME:liblldb>` instead of
`$<TARGET_FILE_BASE_NAME:liblldb>.dll`. The former pattern is what we
use for mingw targets, and it makes the code clearer to use that for
both, as that same expression should do the right thing for both.
To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications
More information about the All-commits
mailing list