There has been a lot of churn in the build process for Python on Windows over the past couple months.
Older versions included a pre-built Python DLL on Windows because of ABI compatibility. That issue is resolved, though, and I thought that was already over by version 7 or earlier. Because other compatibility issues, it was decided that the Windows version could depend on 3.6+ while non-Windows versions might still rely on slightly older versions of Python. That said, I didn't expect an explicit dependency on python36.dll. Please file a bug. I'll look through the revision history and see if I can loop in the folks who've been making changes in this area. I suspect it was an unintended side effect. On Wed, Nov 20, 2019 at 1:59 PM Leonard Mosescu via lldb-dev < lldb-dev@lists.llvm.org> wrote: > I just installed the pre-built LLVM9 binaries on a Windows machine and I > noticed that LLDB.exe imports from python36.dll. Was this an intentional > change from LLVM8? (which doesn't depend on external python DLLs) > > Trying to use the LLDB that comes with LLVM9, you'd get a pop-up > complaining that python36.dll was not found (unless you happen to have on > in your PATH) and LLDB fails to start. > > Thanks, > Leonard. > > ------------------------------ > This email message is for the sole use of the intended recipient(s) and > may contain confidential information. Any unauthorized review, use, > disclosure or distribution is prohibited. If you are not the intended > recipient, please contact the sender by reply email and destroy all copies > of the original message. > ------------------------------ > _______________________________________________ > lldb-dev mailing list > lldb-dev@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev >
_______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev