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 dependency (as we have right now) * Dynamically load Python DLL on startup if it exists, or provide a better error message with instructions * Dynamically load Python DLL on startup if it exists, otherwise disable Python-dependent features * Dynamically load a specific version of the Python DLL if/when needed * Dynamically load any supported Python DLL if/when needed On Thu, Nov 21, 2019 at 1:57 PM Leonard Mosescu <lmose...@nvidia.com> wrote: > 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 <pa...@labath.sk> > *Sent:* Wednesday, November 20, 2019 11:32 PM > *To:* Adrian McCarthy <amcca...@google.com>; Leonard Mosescu < > lmose...@nvidia.com> > *Cc:* lldb-dev@lists.llvm.org <lldb-dev@lists.llvm.org> > *Subject:* 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 > ------------------------------ > 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
