[www] r291643 - Win snapshot: r291484; trying to build lldb with swig 3.0.8

[Zachary Turner via llvm-commits]

Probably I just made a mistake. Is linking against python3.dll the
supported way to get "newest version of python"? We still need to require
>= 3.5 though, people shouldn't be able to use 3.4 or lower
On Wed, Jan 11, 2017 at 9:03 AM Hans Wennborg <hans at chromium.org> wrote:

> On Wed, Jan 11, 2017 at 4:31 AM, Ismail Donmez via llvm-commits
> <llvm-commits at lists.llvm.org> wrote:
> > On Wed, Jan 11, 2017 at 1:30 PM, Ismail Donmez <ismail at i10z.com> wrote:
> >> Hi,
> >>
> >> On Wed, Jan 11, 2017 at 3:08 AM, Hans Wennborg via llvm-commits
> >> <llvm-commits at lists.llvm.org> wrote:
> >>> Author: hans
> >>> Date: Tue Jan 10 20:08:33 2017
> >>> New Revision: 291643
> >>>
> >>> URL: http://llvm.org/viewvc/llvm-project?rev=291643&view=rev
> >>> Log:
> >>> Win snapshot: r291484; trying to build lldb with swig 3.0.8
> >>
> >> Would it be possible to build lldb against Python 3.6 instead? It's
> >> the new stable in the 3.x series.
> >
> > And yes this request is unrelated to this commit :-)
>
> I thought lldb would be linked against python3.dll, but I now see it's
> linked specifically against python35.dll. How does this work for the
> lldb user? I thought we didn't want to require them to have a specific
> version as long as it's Python 3.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20170111/e15fc8c9/attachment.html>