Hmm, I believe it's only supposed to do that if you're doing a debug build. It should only require the Python libraries that match your current build. Is it not doing this?
On Fri, May 19, 2017 at 1:15 PM Vadim Chugunov via lldb-dev < lldb-dev@lists.llvm.org> wrote: > Update: looks like Python detection in CMake now requires debug binaries > to be there as well (e.g. python35_d.dll), otherwise Python support gets > disabled. I am wondering if Python the build machine was installed without > the debug stuff. > > On Fri, May 19, 2017 at 10:52 AM, Vadim Chugunov <vadi...@gmail.com> > wrote: > >> Hi! >> >> I've just noticed that LLDB from the most recent LLVM Windows snapshot >> build has Python scripting disabled. >> Was this done on purpose and for what reason if so? >> > > _______________________________________________ > lldb-dev mailing list > lldb-dev@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev >
_______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
