Re: [lldb-dev] The pre-built Windows LLDB binary has a dependency on an external python36.dll?

FWIW, Python provides stable ABI for a subset of their API. I've actually managed to create a version of LLDB that is Python-optional and Python version-agnostic (for versions 3.3 up). Though given the number of hoops I had to jump through to get

Re: [lldb-dev] The pre-built Windows LLDB binary has a dependency on an external python36.dll?

Yes, I think it's pretty reasonable to expect a specific version of Python, especially if the pre-built Python DLLs for Windows are still built with versions as old as VS 2013. Once you get to VS 2015 or 2017, I think the compatibility improves. Perhaps the best thing for the pre-built LLDB is

Re: [lldb-dev] The pre-built Windows LLDB binary has a dependency on an external python36.dll?

> > * Dynamically load any supported Python DLL if/when needed > That might be tricky since the different versions are not binary compatible in > general. But it is possible, as Apple folks have shown, though it amounts to > building multiple copies of ScriptInterpreterPython and then choosing

Re: [lldb-dev] The pre-built Windows LLDB binary has a dependency on an external python36.dll?

On 22/11/2019 01:26, Adrian McCarthy wrote: Yes, that sounds plausible, but I don't recall for sure.  I think there's a build-time option to say you don't want Python at all, but I can't remember if there was a load-as-needed option. I'm pretty sure we have never had explicit support for

Re: [lldb-dev] The pre-built Windows LLDB binary has a dependency on an external python36.dll?

Yes, that sounds plausible, but I don't recall for sure. I think there's a build-time option to say you don't want Python at all, but I can't remember if there was a load-as-needed option. In any event, the current situation is what it is. What's feasible and worth doing for the future? * Hard

Re: [lldb-dev] The pre-built Windows LLDB binary has a dependency on an external python36.dll?

What kind of behavior did you expect? I could be wrong, but I thought that previous versions of LLDB would use LoadLibrary() instead of linking to the import library? From: Pavel Labath Sent: Wednesday, November 20, 2019 11:32 PM To: Adrian McCarthy ; Leonard

Re: [lldb-dev] The pre-built Windows LLDB binary has a dependency on an external python36.dll?

On 20/11/2019 23:53, Adrian McCarthy via lldb-dev wrote: That said, I didn't expect an explicit dependency on python36.dll. What kind of behavior did you expect? pl ___ lldb-dev mailing list lldb-dev@lists.llvm.org

Re: [lldb-dev] The pre-built Windows LLDB binary has a dependency on an external python36.dll?

Here are some possibly related reviews. Note that some of these were abandoned, but I'm including them because the comments might give some context. https://reviews.llvm.org/D69684 https://reviews.llvm.org/D69931 https://reviews.llvm.org/D67942

Re: [lldb-dev] The pre-built Windows LLDB binary has a dependency on an external python36.dll?

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