Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7

[Vadim Chugunov via lldb-dev]

This seems to work: https://reviews.llvm.org/D27476

On Mon, Dec 5, 2016 at 12:04 PM, Hans Wennborg  wrote:

> The only thing needed to build the installer should be having NSIS
> installed and building the "package" target generated by CMake. The
> other prerequisites are mostly for building the visual studio
> clang-format plugin.
>
> Having said that, you don't even have to build the installer to see
> what goes in it. Just building the "install" target generated by CMake
> will install the same set of files.
>
> I'm not sure how LLDB's cmake files are organized, but in the end
> what's required is invoking the install() command:
> https://cmake.org/cmake/help/v3.0/command/install.html  In LLVM, this
> is done automatically by macros such as add_llvm_executale, etc.
>
> On Mon, Dec 5, 2016 at 11:56 AM, Vadim Chugunov  wrote:
> > Hi Hans,
> >
> > I'd love to help, but I don't have half the tools that
> > build_llvm_package.bat requires installed on my machine.  My setup is to
> > build llvm with msbuild.   Is it possible to build the installer this way
> > too?
> >
> > Can you point me to the specific CMake source that determines what's
> > included in the package?   At a glance, everything from
> > %LLVM%/lib/site-packages is missing.
> >
> > Vadim
> >
> > On Mon, Dec 5, 2016 at 10:41 AM, Hans Wennborg 
> wrote:
> >>
> >> Is anyone working on this?
> >>
> >> I'm happy to include LLDB in the installer, but I'm really not the
> >> best person to be debugging it.
> >>
> >> If more files need to be included in the install, that's configured in
> >> the CMake files (what's installed by the 'install' build target is
> >> also what ends up going into the installer). If it needs more build
> >> flags, patches to build_llvm_package.bat are welsome.
> >
> >
> >
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7

[Zachary Turner via lldb-dev]

I'm OOO this week, but I can look into that when I get back.  What issues
are you having with building LLDB with Ninja?

On Mon, Dec 5, 2016 at 4:04 PM Vadim Chugunov  wrote:

> I am having no luck building LLDB with ninja, and there doesn't seem to be
> a "package" target in the generated msbuild solution file, but here's 
> something
> interesting
> 
> I found in cmake files.  Could this be the reason why Python modules aren't
> being installed on Windows?
>
> On Mon, Dec 5, 2016 at 12:04 PM, Hans Wennborg  wrote:
>
> The only thing needed to build the installer should be having NSIS
> installed and building the "package" target generated by CMake. The
> other prerequisites are mostly for building the visual studio
> clang-format plugin.
>
> Having said that, you don't even have to build the installer to see
> what goes in it. Just building the "install" target generated by CMake
> will install the same set of files.
>
> I'm not sure how LLDB's cmake files are organized, but in the end
> what's required is invoking the install() command:
> https://cmake.org/cmake/help/v3.0/command/install.html  In LLVM, this
> is done automatically by macros such as add_llvm_executale, etc.
>
> On Mon, Dec 5, 2016 at 11:56 AM, Vadim Chugunov  wrote:
> > Hi Hans,
> >
> > I'd love to help, but I don't have half the tools that
> > build_llvm_package.bat requires installed on my machine.  My setup is to
> > build llvm with msbuild.   Is it possible to build the installer this way
> > too?
> >
> > Can you point me to the specific CMake source that determines what's
> > included in the package?   At a glance, everything from
> > %LLVM%/lib/site-packages is missing.
> >
> > Vadim
> >
> > On Mon, Dec 5, 2016 at 10:41 AM, Hans Wennborg 
> wrote:
> >>
> >> Is anyone working on this?
> >>
> >> I'm happy to include LLDB in the installer, but I'm really not the
> >> best person to be debugging it.
> >>
> >> If more files need to be included in the install, that's configured in
> >> the CMake files (what's installed by the 'install' build target is
> >> also what ends up going into the installer). If it needs more build
> >> flags, patches to build_llvm_package.bat are welsome.
> >
> >
> >
>
>
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7

[Vadim Chugunov via lldb-dev]

I am having no luck building LLDB with ninja, and there doesn't seem to be
a "package" target in the generated msbuild solution file, but here's something
interesting

I found in cmake files.  Could this be the reason why Python modules aren't
being installed on Windows?

On Mon, Dec 5, 2016 at 12:04 PM, Hans Wennborg  wrote:

> The only thing needed to build the installer should be having NSIS
> installed and building the "package" target generated by CMake. The
> other prerequisites are mostly for building the visual studio
> clang-format plugin.
>
> Having said that, you don't even have to build the installer to see
> what goes in it. Just building the "install" target generated by CMake
> will install the same set of files.
>
> I'm not sure how LLDB's cmake files are organized, but in the end
> what's required is invoking the install() command:
> https://cmake.org/cmake/help/v3.0/command/install.html  In LLVM, this
> is done automatically by macros such as add_llvm_executale, etc.
>
> On Mon, Dec 5, 2016 at 11:56 AM, Vadim Chugunov  wrote:
> > Hi Hans,
> >
> > I'd love to help, but I don't have half the tools that
> > build_llvm_package.bat requires installed on my machine.  My setup is to
> > build llvm with msbuild.   Is it possible to build the installer this way
> > too?
> >
> > Can you point me to the specific CMake source that determines what's
> > included in the package?   At a glance, everything from
> > %LLVM%/lib/site-packages is missing.
> >
> > Vadim
> >
> > On Mon, Dec 5, 2016 at 10:41 AM, Hans Wennborg 
> wrote:
> >>
> >> Is anyone working on this?
> >>
> >> I'm happy to include LLDB in the installer, but I'm really not the
> >> best person to be debugging it.
> >>
> >> If more files need to be included in the install, that's configured in
> >> the CMake files (what's installed by the 'install' build target is
> >> also what ends up going into the installer). If it needs more build
> >> flags, patches to build_llvm_package.bat are welsome.
> >
> >
> >
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7

[Hans Wennborg via lldb-dev]

The only thing needed to build the installer should be having NSIS
installed and building the "package" target generated by CMake. The
other prerequisites are mostly for building the visual studio
clang-format plugin.

Having said that, you don't even have to build the installer to see
what goes in it. Just building the "install" target generated by CMake
will install the same set of files.

I'm not sure how LLDB's cmake files are organized, but in the end
what's required is invoking the install() command:
https://cmake.org/cmake/help/v3.0/command/install.html  In LLVM, this
is done automatically by macros such as add_llvm_executale, etc.

On Mon, Dec 5, 2016 at 11:56 AM, Vadim Chugunov  wrote:
> Hi Hans,
>
> I'd love to help, but I don't have half the tools that
> build_llvm_package.bat requires installed on my machine.  My setup is to
> build llvm with msbuild.   Is it possible to build the installer this way
> too?
>
> Can you point me to the specific CMake source that determines what's
> included in the package?   At a glance, everything from
> %LLVM%/lib/site-packages is missing.
>
> Vadim
>
> On Mon, Dec 5, 2016 at 10:41 AM, Hans Wennborg  wrote:
>>
>> Is anyone working on this?
>>
>> I'm happy to include LLDB in the installer, but I'm really not the
>> best person to be debugging it.
>>
>> If more files need to be included in the install, that's configured in
>> the CMake files (what's installed by the 'install' build target is
>> also what ends up going into the installer). If it needs more build
>> flags, patches to build_llvm_package.bat are welsome.
>
>
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7

[Vadim Chugunov via lldb-dev]

Hi Hans,

I'd love to help, but I don't have half the tools that build_llvm_package.bat
requires installed on my machine.  My setup is to build llvm with msbuild.
  Is it possible to build the installer this way too?

Can you point me to the specific CMake source that determines what's
included in the package?   At a glance, everything from
%LLVM%/lib/site-packages is missing.

Vadim

On Mon, Dec 5, 2016 at 10:41 AM, Hans Wennborg  wrote:

> Is anyone working on this?
>
I'm happy to include LLDB in the installer, but I'm really not the
> best person to be debugging it.
>
> If more files need to be included in the install, that's configured in
> the CMake files (what's installed by the 'install' build target is
> also what ends up going into the installer). If it needs more build
> flags, patches to build_llvm_package.bat are welsome.
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7

[Hans Wennborg via lldb-dev]

Is anyone working on this?

I'm happy to include LLDB in the installer, but I'm really not the
best person to be debugging it.

If more files need to be included in the install, that's configured in
the CMake files (what's installed by the 'install' build target is
also what ends up going into the installer). If it needs more build
flags, patches to build_llvm_package.bat are welsome.

Thanks,
Hans

On Mon, Nov 28, 2016 at 10:17 AM, Zachary Turner <ztur...@google.com> wrote:
> I overlooked that part of it, but yes that is another separate issue.  (BTW,
> _lldb.pyd is simply a symlink to liblldb.dll).
>
> In any case, yea I think the entire lib/site-packages folder needs to be
> included.
>
> On Mon, Nov 28, 2016 at 10:15 AM Vadim Chugunov <vadi...@gmail.com> wrote:
>>
>> Please correct me if I'm wrong, but isn't the issue here that LLDB's
>> Python support files don't get packaged into the Windows installer?   Does
>> packaging them somehow depend on knowing what the Python installation path
>> is?
>>
>> On Mon, Nov 28, 2016 at 10:09 AM, Hans Wennborg <h...@chromium.org> wrote:
>>>
>>> The snapshots are built with the script in
>>> utils/release/build_llvm_package.bat. It's currently passing
>>> -DLLDB_RELOCATABLE_PYTHON=1 and  -DPYTHON_HOME=.
>>>
>>> I was planning on trying to build a new snapshot today and can add
>>> -DLLDB_DEFAULT_PYTHON_HOME if you think that will help.
>>>
>>> On Mon, Nov 28, 2016 at 9:51 AM, Zachary Turner <ztur...@google.com>
>>> wrote:
>>> > So it sounds like you're saying that in order for Python support to
>>> > work as
>>> > part of an LLDB shipped in the installer, we need to do set 3 variables
>>> > at
>>> > CMake time.
>>> >
>>> > 1) -DLLDB_RELOCATABLE_PYTHON=TRUE
>>> > 2) -DPYTHON_HOME = 
>>> > 3) -DLLDB_DEFAULT_PYTHON_HOME=TRUE
>>> >
>>> > Now because of #3, the lldb shipped in the installer will use the
>>> > PYTHONHOME
>>> > system environment variable to locate python, which must point to a
>>> > valid
>>> > Python 3.5 installation.  Is this correct?
>>> >
>>> > On Mon, Nov 28, 2016 at 9:35 AM Ted Woodward
>>> > <ted.woodw...@codeaurora.org>
>>> > wrote:
>>> >>
>>> >> Windows has no concept of a default python installation, and I can’t
>>> >> be
>>> >> sure what version of python my users have, if any, so I need to solve
>>> >> 2
>>> >> problems:
>>> >>
>>> >> 1)  Where is python when I’m building?
>>> >>
>>> >> 2)  Where is python when I’m running?
>>> >>
>>> >>
>>> >>
>>> >> To solve #1, I set LLDB_RELOCATABLE_PYTHON to TRUE, and PYTHON_HOME to
>>> >> my
>>> >> python installation (on our buildbots, c:/python351).
>>> >>
>>> >>
>>> >>
>>> >> #2 only needs to be solved if the machine you’re running on doesn’t
>>> >> have
>>> >> the same python installation, in PYTHON_HOME above. To do that, I’ve
>>> >> added
>>> >> code to set a cmake path LLDB_DEFAULT_PYTHONHOME, which I pass as a
>>> >> macro
>>> >> down to InitializePythonHome in
>>> >> source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp,
>>> >> and
>>> >> call Py_SetPythonHome with it. My installations have the python dll
>>> >> and
>>> >> python library directory. We put the library in /lib/python35
>>> >> and
>>> >> the dll in /bin.
>>> >>
>>> >> --
>>> >>
>>> >> Qualcomm Innovation Center, Inc.
>>> >>
>>> >> The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
>>> >> a
>>> >> Linux Foundation Collaborative Project
>>> >>
>>> >>
>>> >>
>>> >> From: Zachary Turner [mailto:ztur...@google.com]
>>> >> Sent: Wednesday, November 23, 2016 12:40 PM
>>> >> To: Vadim Chugunov <vadi...@gmail.com>
>>> >> Cc: Reid Kleckner <r...@google.com>; Hans Wennborg <h...@chromium.org>;
>>> >> LLDB <lldb-dev@lists.llvm.org>; Ted Woodward
>>> >> <ted.woodw...@codeaurora.org>
>>> >> Subject: Re: [lldb-d

Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7

[Vadim Chugunov via lldb-dev]

Is there a tarball somewhere that I can pull those files out from?

I tried with an older build I have on my machine; and copying site-packages
over into %LLVM%\lib did allow lldb module loading to get a bit further,
but it still failed because SWIG-generated wrapper does not match the .pyd
module.

On Mon, Nov 28, 2016 at 10:28 AM, Zachary Turner <ztur...@google.com> wrote:

> BTW, _lldb.pyd is just a symlink of liblldb.dll.  Perhaps you could try
> creating the symlink manually and copying the other files (e.g.
> embedded_interpreter.py, six.py, etc) over to see if it works.  If it does,
> it would at least confirm that this is everything we need to do to get it
> working for you, so that we can have some confidence the next release
> doesn't have the problems.
>
> On Mon, Nov 28, 2016 at 10:25 AM Vadim Chugunov <vadi...@gmail.com> wrote:
>
>> At least on my machine, finding Python is not the problem, because Python
>> installer has added C:\Python35 to the PATH.  (It can also be found in the
>> Registry at
>> HKLM\SOFTWARE\Python\PythonCore\3.5-32\InstallPath).
>>
>>
>> On Mon, Nov 28, 2016 at 10:17 AM, Zachary Turner <ztur...@google.com>
>> wrote:
>>
>> I overlooked that part of it, but yes that is another separate issue.
>>  (BTW, _lldb.pyd is simply a symlink to liblldb.dll).
>>
>> In any case, yea I think the entire lib/site-packages folder needs to be
>> included.
>>
>> On Mon, Nov 28, 2016 at 10:15 AM Vadim Chugunov <vadi...@gmail.com>
>> wrote:
>>
>> Please correct me if I'm wrong, but isn't the issue here that LLDB's
>> Python support files don't get packaged into the Windows installer?   Does
>> packaging them somehow depend on knowing what the Python installation path
>> is?
>>
>> On Mon, Nov 28, 2016 at 10:09 AM, Hans Wennborg <h...@chromium.org>
>> wrote:
>>
>> The snapshots are built with the script in
>> utils/release/build_llvm_package.bat. It's currently passing
>> -DLLDB_RELOCATABLE_PYTHON=1 and  -DPYTHON_HOME=.
>>
>> I was planning on trying to build a new snapshot today and can add
>> -DLLDB_DEFAULT_PYTHON_HOME if you think that will help.
>>
>> On Mon, Nov 28, 2016 at 9:51 AM, Zachary Turner <ztur...@google.com>
>> wrote:
>> > So it sounds like you're saying that in order for Python support to
>> work as
>> > part of an LLDB shipped in the installer, we need to do set 3 variables
>> at
>> > CMake time.
>> >
>> > 1) -DLLDB_RELOCATABLE_PYTHON=TRUE
>> > 2) -DPYTHON_HOME = 
>> > 3) -DLLDB_DEFAULT_PYTHON_HOME=TRUE
>> >
>> > Now because of #3, the lldb shipped in the installer will use the
>> PYTHONHOME
>> > system environment variable to locate python, which must point to a
>> valid
>> > Python 3.5 installation.  Is this correct?
>> >
>> > On Mon, Nov 28, 2016 at 9:35 AM Ted Woodward <
>> ted.woodw...@codeaurora.org>
>> > wrote:
>> >>
>> >> Windows has no concept of a default python installation, and I can’t be
>> >> sure what version of python my users have, if any, so I need to solve 2
>> >> problems:
>> >>
>> >> 1)  Where is python when I’m building?
>> >>
>> >> 2)  Where is python when I’m running?
>> >>
>> >>
>> >>
>> >> To solve #1, I set LLDB_RELOCATABLE_PYTHON to TRUE, and PYTHON_HOME to
>> my
>> >> python installation (on our buildbots, c:/python351).
>> >>
>> >>
>> >>
>> >> #2 only needs to be solved if the machine you’re running on doesn’t
>> have
>> >> the same python installation, in PYTHON_HOME above. To do that, I’ve
>> added
>> >> code to set a cmake path LLDB_DEFAULT_PYTHONHOME, which I pass as a
>> macro
>> >> down to InitializePythonHome in
>> >> source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp,
>> and
>> >> call Py_SetPythonHome with it. My installations have the python dll and
>> >> python library directory. We put the library in /lib/python35
>> and
>> >> the dll in /bin.
>> >>
>> >> --
>> >>
>> >> Qualcomm Innovation Center, Inc.
>> >>
>> >> The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
>> a
>> >> Linux Foundation Collaborative Project
>> >>
>> >>
>> >>
>> >> From: Zachary Turner [mailto:ztur...@google.com]
>> >> 

Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7

[Ted Woodward via lldb-dev]

LLDB_DEFAULT_PYTHONHOME is an internal thing; I haven’t upstreamed it – for a 
while, it conflicted with Zach’s implementation, but I redid it, and everything 
is happy now. If you think it would be useful, I could upstream it. It’s fairly 
small, and plays nice with Zach’s Python stuff.

 

The problem it solves is “where is my python?” on Windows. If you know you’ll 
be running on a system with the same python installation as the build system, 
then you don’t need it. Or if you can tell your users to install the same 
python you built with, in the same location, you’re OK. I can’t do that, so 
instead I ship python, and tell lldb where to find it at build time.

 

We copy over the full site-packages directory that is created by the lldb 
build, and end up with this directory structure:

bin/lldb.exe

bin/liblldb.dll

bin/python35.dll

lib/python35

lib/site-packages

 

--

Qualcomm Innovation Center, Inc.

The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux 
Foundation Collaborative Project

 

From: Zachary Turner [mailto:ztur...@google.com] 
Sent: Monday, November 28, 2016 12:17 PM
To: Vadim Chugunov <vadi...@gmail.com>; Hans Wennborg <h...@chromium.org>
Cc: Ted Woodward <ted.woodw...@codeaurora.org>; Reid Kleckner 
<r...@google.com>; LLDB <lldb-dev@lists.llvm.org>
Subject: Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7

 

I overlooked that part of it, but yes that is another separate issue.  (BTW, 
_lldb.pyd is simply a symlink to liblldb.dll).  

 

In any case, yea I think the entire lib/site-packages folder needs to be 
included.

 

On Mon, Nov 28, 2016 at 10:15 AM Vadim Chugunov <vadi...@gmail.com 
<mailto:vadi...@gmail.com> > wrote:

Please correct me if I'm wrong, but isn't the issue here that LLDB's Python 
support files don't get packaged into the Windows installer?   Does packaging 
them somehow depend on knowing what the Python installation path is?

 

On Mon, Nov 28, 2016 at 10:09 AM, Hans Wennborg <h...@chromium.org 
<mailto:h...@chromium.org> > wrote:

The snapshots are built with the script in
utils/release/build_llvm_package.bat. It's currently passing
-DLLDB_RELOCATABLE_PYTHON=1 and  -DPYTHON_HOME=.

I was planning on trying to build a new snapshot today and can add
-DLLDB_DEFAULT_PYTHON_HOME if you think that will help.

On Mon, Nov 28, 2016 at 9:51 AM, Zachary Turner <ztur...@google.com 
<mailto:ztur...@google.com> > wrote:
> So it sounds like you're saying that in order for Python support to work as
> part of an LLDB shipped in the installer, we need to do set 3 variables at
> CMake time.
>
> 1) -DLLDB_RELOCATABLE_PYTHON=TRUE
> 2) -DPYTHON_HOME = 
> 3) -DLLDB_DEFAULT_PYTHON_HOME=TRUE
>
> Now because of #3, the lldb shipped in the installer will use the PYTHONHOME
> system environment variable to locate python, which must point to a valid
> Python 3.5 installation.  Is this correct?
>
> On Mon, Nov 28, 2016 at 9:35 AM Ted Woodward <ted.woodw...@codeaurora.org 
> <mailto:ted.woodw...@codeaurora.org> >
> wrote:
>>
>> Windows has no concept of a default python installation, and I can’t be
>> sure what version of python my users have, if any, so I need to solve 2
>> problems:
>>
>> 1)  Where is python when I’m building?
>>
>> 2)  Where is python when I’m running?
>>
>>
>>
>> To solve #1, I set LLDB_RELOCATABLE_PYTHON to TRUE, and PYTHON_HOME to my
>> python installation (on our buildbots, c:/python351).
>>
>>
>>
>> #2 only needs to be solved if the machine you’re running on doesn’t have
>> the same python installation, in PYTHON_HOME above. To do that, I’ve added
>> code to set a cmake path LLDB_DEFAULT_PYTHONHOME, which I pass as a macro
>> down to InitializePythonHome in
>> source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp, and
>> call Py_SetPythonHome with it. My installations have the python dll and
>> python library directory. We put the library in /lib/python35 and
>> the dll in /bin.
>>
>> --
>>
>> Qualcomm Innovation Center, Inc.
>>
>> The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a
>> Linux Foundation Collaborative Project
>>
>>
>>
>> From: Zachary Turner [mailto:ztur...@google.com <mailto:ztur...@google.com> ]
>> Sent: Wednesday, November 23, 2016 12:40 PM
>> To: Vadim Chugunov <vadi...@gmail.com <mailto:vadi...@gmail.com> >
>> Cc: Reid Kleckner <r...@google.com <mailto:r...@google.com> >; Hans Wennborg 
>> <h...@chromium.org <mailto:h...@chromium.org> >;
>> LLDB <lldb-dev@lists.llvm.org <mailto:lldb-dev@lists.llvm.org> >; Ted 
>> Woodward <ted.woodw...@codeaurora.or

Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7

[Zachary Turner via lldb-dev]

BTW, _lldb.pyd is just a symlink of liblldb.dll.  Perhaps you could try
creating the symlink manually and copying the other files (e.g.
embedded_interpreter.py, six.py, etc) over to see if it works.  If it does,
it would at least confirm that this is everything we need to do to get it
working for you, so that we can have some confidence the next release
doesn't have the problems.

On Mon, Nov 28, 2016 at 10:25 AM Vadim Chugunov <vadi...@gmail.com> wrote:

> At least on my machine, finding Python is not the problem, because Python
> installer has added C:\Python35 to the PATH.  (It can also be found in the
> Registry at
> HKLM\SOFTWARE\Python\PythonCore\3.5-32\InstallPath).
>
>
> On Mon, Nov 28, 2016 at 10:17 AM, Zachary Turner <ztur...@google.com>
> wrote:
>
> I overlooked that part of it, but yes that is another separate issue.
>  (BTW, _lldb.pyd is simply a symlink to liblldb.dll).
>
> In any case, yea I think the entire lib/site-packages folder needs to be
> included.
>
> On Mon, Nov 28, 2016 at 10:15 AM Vadim Chugunov <vadi...@gmail.com> wrote:
>
> Please correct me if I'm wrong, but isn't the issue here that LLDB's
> Python support files don't get packaged into the Windows installer?   Does
> packaging them somehow depend on knowing what the Python installation path
> is?
>
> On Mon, Nov 28, 2016 at 10:09 AM, Hans Wennborg <h...@chromium.org> wrote:
>
> The snapshots are built with the script in
> utils/release/build_llvm_package.bat. It's currently passing
> -DLLDB_RELOCATABLE_PYTHON=1 and  -DPYTHON_HOME=.
>
> I was planning on trying to build a new snapshot today and can add
> -DLLDB_DEFAULT_PYTHON_HOME if you think that will help.
>
> On Mon, Nov 28, 2016 at 9:51 AM, Zachary Turner <ztur...@google.com>
> wrote:
> > So it sounds like you're saying that in order for Python support to work
> as
> > part of an LLDB shipped in the installer, we need to do set 3 variables
> at
> > CMake time.
> >
> > 1) -DLLDB_RELOCATABLE_PYTHON=TRUE
> > 2) -DPYTHON_HOME = 
> > 3) -DLLDB_DEFAULT_PYTHON_HOME=TRUE
> >
> > Now because of #3, the lldb shipped in the installer will use the
> PYTHONHOME
> > system environment variable to locate python, which must point to a valid
> > Python 3.5 installation.  Is this correct?
> >
> > On Mon, Nov 28, 2016 at 9:35 AM Ted Woodward <
> ted.woodw...@codeaurora.org>
> > wrote:
> >>
> >> Windows has no concept of a default python installation, and I can’t be
> >> sure what version of python my users have, if any, so I need to solve 2
> >> problems:
> >>
> >> 1)  Where is python when I’m building?
> >>
> >> 2)  Where is python when I’m running?
> >>
> >>
> >>
> >> To solve #1, I set LLDB_RELOCATABLE_PYTHON to TRUE, and PYTHON_HOME to
> my
> >> python installation (on our buildbots, c:/python351).
> >>
> >>
> >>
> >> #2 only needs to be solved if the machine you’re running on doesn’t have
> >> the same python installation, in PYTHON_HOME above. To do that, I’ve
> added
> >> code to set a cmake path LLDB_DEFAULT_PYTHONHOME, which I pass as a
> macro
> >> down to InitializePythonHome in
> >> source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp, and
> >> call Py_SetPythonHome with it. My installations have the python dll and
> >> python library directory. We put the library in /lib/python35
> and
> >> the dll in /bin.
> >>
> >> --
> >>
> >> Qualcomm Innovation Center, Inc.
> >>
> >> The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a
> >> Linux Foundation Collaborative Project
> >>
> >>
> >>
> >> From: Zachary Turner [mailto:ztur...@google.com]
> >> Sent: Wednesday, November 23, 2016 12:40 PM
> >> To: Vadim Chugunov <vadi...@gmail.com>
> >> Cc: Reid Kleckner <r...@google.com>; Hans Wennborg <h...@chromium.org>;
> >> LLDB <lldb-dev@lists.llvm.org>; Ted Woodward <
> ted.woodw...@codeaurora.org>
> >> Subject: Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7
> >>
> >>
> >>
> >> I believe the way to fix this is going to be building LLDB for the
> >> installer with LLDB_RELOCATABLE_PYTHON=1 at CMake time
> >>
> >>
> >>
> >> +Ted, since I believe he is one of the few people currently using this
> >> flag.
> >>
> >> On Wed, Nov 23, 2016 at 10:36 AM Vadim Chugunov <vadi...@gmail.com>
> wrote:
> 

Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7

[Vadim Chugunov via lldb-dev]

At least on my machine, finding Python is not the problem, because Python
installer has added C:\Python35 to the PATH.  (It can also be found in the
Registry at
HKLM\SOFTWARE\Python\PythonCore\3.5-32\InstallPath).


On Mon, Nov 28, 2016 at 10:17 AM, Zachary Turner <ztur...@google.com> wrote:

> I overlooked that part of it, but yes that is another separate issue.
>  (BTW, _lldb.pyd is simply a symlink to liblldb.dll).
>
> In any case, yea I think the entire lib/site-packages folder needs to be
> included.
>
> On Mon, Nov 28, 2016 at 10:15 AM Vadim Chugunov <vadi...@gmail.com> wrote:
>
>> Please correct me if I'm wrong, but isn't the issue here that LLDB's
>> Python support files don't get packaged into the Windows installer?   Does
>> packaging them somehow depend on knowing what the Python installation path
>> is?
>>
>> On Mon, Nov 28, 2016 at 10:09 AM, Hans Wennborg <h...@chromium.org>
>> wrote:
>>
>> The snapshots are built with the script in
>> utils/release/build_llvm_package.bat. It's currently passing
>> -DLLDB_RELOCATABLE_PYTHON=1 and  -DPYTHON_HOME=.
>>
>> I was planning on trying to build a new snapshot today and can add
>> -DLLDB_DEFAULT_PYTHON_HOME if you think that will help.
>>
>> On Mon, Nov 28, 2016 at 9:51 AM, Zachary Turner <ztur...@google.com>
>> wrote:
>> > So it sounds like you're saying that in order for Python support to
>> work as
>> > part of an LLDB shipped in the installer, we need to do set 3 variables
>> at
>> > CMake time.
>> >
>> > 1) -DLLDB_RELOCATABLE_PYTHON=TRUE
>> > 2) -DPYTHON_HOME = 
>> > 3) -DLLDB_DEFAULT_PYTHON_HOME=TRUE
>> >
>> > Now because of #3, the lldb shipped in the installer will use the
>> PYTHONHOME
>> > system environment variable to locate python, which must point to a
>> valid
>> > Python 3.5 installation.  Is this correct?
>> >
>> > On Mon, Nov 28, 2016 at 9:35 AM Ted Woodward <
>> ted.woodw...@codeaurora.org>
>> > wrote:
>> >>
>> >> Windows has no concept of a default python installation, and I can’t be
>> >> sure what version of python my users have, if any, so I need to solve 2
>> >> problems:
>> >>
>> >> 1)  Where is python when I’m building?
>> >>
>> >> 2)  Where is python when I’m running?
>> >>
>> >>
>> >>
>> >> To solve #1, I set LLDB_RELOCATABLE_PYTHON to TRUE, and PYTHON_HOME to
>> my
>> >> python installation (on our buildbots, c:/python351).
>> >>
>> >>
>> >>
>> >> #2 only needs to be solved if the machine you’re running on doesn’t
>> have
>> >> the same python installation, in PYTHON_HOME above. To do that, I’ve
>> added
>> >> code to set a cmake path LLDB_DEFAULT_PYTHONHOME, which I pass as a
>> macro
>> >> down to InitializePythonHome in
>> >> source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp,
>> and
>> >> call Py_SetPythonHome with it. My installations have the python dll and
>> >> python library directory. We put the library in /lib/python35
>> and
>> >> the dll in /bin.
>> >>
>> >> --
>> >>
>> >> Qualcomm Innovation Center, Inc.
>> >>
>> >> The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
>> a
>> >> Linux Foundation Collaborative Project
>> >>
>> >>
>> >>
>> >> From: Zachary Turner [mailto:ztur...@google.com]
>> >> Sent: Wednesday, November 23, 2016 12:40 PM
>> >> To: Vadim Chugunov <vadi...@gmail.com>
>> >> Cc: Reid Kleckner <r...@google.com>; Hans Wennborg <h...@chromium.org>;
>> >> LLDB <lldb-dev@lists.llvm.org>; Ted Woodward <
>> ted.woodw...@codeaurora.org>
>> >> Subject: Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7
>> >>
>> >>
>> >>
>> >> I believe the way to fix this is going to be building LLDB for the
>> >> installer with LLDB_RELOCATABLE_PYTHON=1 at CMake time
>> >>
>> >>
>> >>
>> >> +Ted, since I believe he is one of the few people currently using this
>> >> flag.
>> >>
>> >> On Wed, Nov 23, 2016 at 10:36 AM Vadim Chugunov <vadi...@gmail.com>
>> wrote:
>> >>
>> >> This is still broken in the October snapshot.   Do you know which
>>

Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7

[Zachary Turner via lldb-dev]

I overlooked that part of it, but yes that is another separate issue.
 (BTW, _lldb.pyd is simply a symlink to liblldb.dll).

In any case, yea I think the entire lib/site-packages folder needs to be
included.

On Mon, Nov 28, 2016 at 10:15 AM Vadim Chugunov <vadi...@gmail.com> wrote:

> Please correct me if I'm wrong, but isn't the issue here that LLDB's
> Python support files don't get packaged into the Windows installer?   Does
> packaging them somehow depend on knowing what the Python installation path
> is?
>
> On Mon, Nov 28, 2016 at 10:09 AM, Hans Wennborg <h...@chromium.org> wrote:
>
> The snapshots are built with the script in
> utils/release/build_llvm_package.bat. It's currently passing
> -DLLDB_RELOCATABLE_PYTHON=1 and  -DPYTHON_HOME=.
>
> I was planning on trying to build a new snapshot today and can add
> -DLLDB_DEFAULT_PYTHON_HOME if you think that will help.
>
> On Mon, Nov 28, 2016 at 9:51 AM, Zachary Turner <ztur...@google.com>
> wrote:
> > So it sounds like you're saying that in order for Python support to work
> as
> > part of an LLDB shipped in the installer, we need to do set 3 variables
> at
> > CMake time.
> >
> > 1) -DLLDB_RELOCATABLE_PYTHON=TRUE
> > 2) -DPYTHON_HOME = 
> > 3) -DLLDB_DEFAULT_PYTHON_HOME=TRUE
> >
> > Now because of #3, the lldb shipped in the installer will use the
> PYTHONHOME
> > system environment variable to locate python, which must point to a valid
> > Python 3.5 installation.  Is this correct?
> >
> > On Mon, Nov 28, 2016 at 9:35 AM Ted Woodward <
> ted.woodw...@codeaurora.org>
> > wrote:
> >>
> >> Windows has no concept of a default python installation, and I can’t be
> >> sure what version of python my users have, if any, so I need to solve 2
> >> problems:
> >>
> >> 1)  Where is python when I’m building?
> >>
> >> 2)  Where is python when I’m running?
> >>
> >>
> >>
> >> To solve #1, I set LLDB_RELOCATABLE_PYTHON to TRUE, and PYTHON_HOME to
> my
> >> python installation (on our buildbots, c:/python351).
> >>
> >>
> >>
> >> #2 only needs to be solved if the machine you’re running on doesn’t have
> >> the same python installation, in PYTHON_HOME above. To do that, I’ve
> added
> >> code to set a cmake path LLDB_DEFAULT_PYTHONHOME, which I pass as a
> macro
> >> down to InitializePythonHome in
> >> source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp, and
> >> call Py_SetPythonHome with it. My installations have the python dll and
> >> python library directory. We put the library in /lib/python35
> and
> >> the dll in /bin.
> >>
> >> --
> >>
> >> Qualcomm Innovation Center, Inc.
> >>
> >> The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a
> >> Linux Foundation Collaborative Project
> >>
> >>
> >>
> >> From: Zachary Turner [mailto:ztur...@google.com]
> >> Sent: Wednesday, November 23, 2016 12:40 PM
> >> To: Vadim Chugunov <vadi...@gmail.com>
> >> Cc: Reid Kleckner <r...@google.com>; Hans Wennborg <h...@chromium.org>;
> >> LLDB <lldb-dev@lists.llvm.org>; Ted Woodward <
> ted.woodw...@codeaurora.org>
> >> Subject: Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7
> >>
> >>
> >>
> >> I believe the way to fix this is going to be building LLDB for the
> >> installer with LLDB_RELOCATABLE_PYTHON=1 at CMake time
> >>
> >>
> >>
> >> +Ted, since I believe he is one of the few people currently using this
> >> flag.
> >>
> >> On Wed, Nov 23, 2016 at 10:36 AM Vadim Chugunov <vadi...@gmail.com>
> wrote:
> >>
> >> This is still broken in the October snapshot.   Do you know which script
> >> is used to build the Windows installer?
> >>
> >>
> >>
> >> On Tue, Oct 11, 2016 at 6:24 PM, Zachary Turner <ztur...@google.com>
> >> wrote:
> >>
> >> I think it is a problem with the way we built lldb.  I will look into
> what
> >> additional steps we need to take when making the prebuilt binary so
> that it
> >> works next time.
> >>
> >>
> >>
> >> On Tue, Oct 11, 2016 at 6:20 PM Vadim Chugunov <vadi...@gmail.com>
> wrote:
> >>
> >> Nope, that didn't help.
> >>
> >>
> >>
> >> On Tue, Oct 11, 2016 at 5:16 PM, Zachary Turner <ztur...

Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7

[Vadim Chugunov via lldb-dev]

Please correct me if I'm wrong, but isn't the issue here that LLDB's Python
support files don't get packaged into the Windows installer?   Does
packaging them somehow depend on knowing what the Python installation path
is?

On Mon, Nov 28, 2016 at 10:09 AM, Hans Wennborg <h...@chromium.org> wrote:

> The snapshots are built with the script in
> utils/release/build_llvm_package.bat. It's currently passing
> -DLLDB_RELOCATABLE_PYTHON=1 and  -DPYTHON_HOME=.
>
> I was planning on trying to build a new snapshot today and can add
> -DLLDB_DEFAULT_PYTHON_HOME if you think that will help.
>
> On Mon, Nov 28, 2016 at 9:51 AM, Zachary Turner <ztur...@google.com>
> wrote:
> > So it sounds like you're saying that in order for Python support to work
> as
> > part of an LLDB shipped in the installer, we need to do set 3 variables
> at
> > CMake time.
> >
> > 1) -DLLDB_RELOCATABLE_PYTHON=TRUE
> > 2) -DPYTHON_HOME = 
> > 3) -DLLDB_DEFAULT_PYTHON_HOME=TRUE
> >
> > Now because of #3, the lldb shipped in the installer will use the
> PYTHONHOME
> > system environment variable to locate python, which must point to a valid
> > Python 3.5 installation.  Is this correct?
> >
> > On Mon, Nov 28, 2016 at 9:35 AM Ted Woodward <
> ted.woodw...@codeaurora.org>
> > wrote:
> >>
> >> Windows has no concept of a default python installation, and I can’t be
> >> sure what version of python my users have, if any, so I need to solve 2
> >> problems:
> >>
> >> 1)  Where is python when I’m building?
> >>
> >> 2)  Where is python when I’m running?
> >>
> >>
> >>
> >> To solve #1, I set LLDB_RELOCATABLE_PYTHON to TRUE, and PYTHON_HOME to
> my
> >> python installation (on our buildbots, c:/python351).
> >>
> >>
> >>
> >> #2 only needs to be solved if the machine you’re running on doesn’t have
> >> the same python installation, in PYTHON_HOME above. To do that, I’ve
> added
> >> code to set a cmake path LLDB_DEFAULT_PYTHONHOME, which I pass as a
> macro
> >> down to InitializePythonHome in
> >> source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp,
> and
> >> call Py_SetPythonHome with it. My installations have the python dll and
> >> python library directory. We put the library in /lib/python35
> and
> >> the dll in /bin.
> >>
> >> --
> >>
> >> Qualcomm Innovation Center, Inc.
> >>
> >> The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a
> >> Linux Foundation Collaborative Project
> >>
> >>
> >>
> >> From: Zachary Turner [mailto:ztur...@google.com]
> >> Sent: Wednesday, November 23, 2016 12:40 PM
> >> To: Vadim Chugunov <vadi...@gmail.com>
> >> Cc: Reid Kleckner <r...@google.com>; Hans Wennborg <h...@chromium.org>;
> >> LLDB <lldb-dev@lists.llvm.org>; Ted Woodward <
> ted.woodw...@codeaurora.org>
> >> Subject: Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7
> >>
> >>
> >>
> >> I believe the way to fix this is going to be building LLDB for the
> >> installer with LLDB_RELOCATABLE_PYTHON=1 at CMake time
> >>
> >>
> >>
> >> +Ted, since I believe he is one of the few people currently using this
> >> flag.
> >>
> >> On Wed, Nov 23, 2016 at 10:36 AM Vadim Chugunov <vadi...@gmail.com>
> wrote:
> >>
> >> This is still broken in the October snapshot.   Do you know which script
> >> is used to build the Windows installer?
> >>
> >>
> >>
> >> On Tue, Oct 11, 2016 at 6:24 PM, Zachary Turner <ztur...@google.com>
> >> wrote:
> >>
> >> I think it is a problem with the way we built lldb.  I will look into
> what
> >> additional steps we need to take when making the prebuilt binary so
> that it
> >> works next time.
> >>
> >>
> >>
> >> On Tue, Oct 11, 2016 at 6:20 PM Vadim Chugunov <vadi...@gmail.com>
> wrote:
> >>
> >> Nope, that didn't help.
> >>
> >>
> >>
> >> On Tue, Oct 11, 2016 at 5:16 PM, Zachary Turner <ztur...@google.com>
> >> wrote:
> >>
> >> I may know what this is.  Can you try setting PYTHONPATH though to point
> >> to your Python 3.5 installation though and see if it fixes it?  (I don't
> >> think it will, but let's try anyway)
> >>
> >>
> >>
> >

Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7

[Hans Wennborg via lldb-dev]

The snapshots are built with the script in
utils/release/build_llvm_package.bat. It's currently passing
-DLLDB_RELOCATABLE_PYTHON=1 and  -DPYTHON_HOME=.

I was planning on trying to build a new snapshot today and can add
-DLLDB_DEFAULT_PYTHON_HOME if you think that will help.

On Mon, Nov 28, 2016 at 9:51 AM, Zachary Turner <ztur...@google.com> wrote:
> So it sounds like you're saying that in order for Python support to work as
> part of an LLDB shipped in the installer, we need to do set 3 variables at
> CMake time.
>
> 1) -DLLDB_RELOCATABLE_PYTHON=TRUE
> 2) -DPYTHON_HOME = 
> 3) -DLLDB_DEFAULT_PYTHON_HOME=TRUE
>
> Now because of #3, the lldb shipped in the installer will use the PYTHONHOME
> system environment variable to locate python, which must point to a valid
> Python 3.5 installation.  Is this correct?
>
> On Mon, Nov 28, 2016 at 9:35 AM Ted Woodward <ted.woodw...@codeaurora.org>
> wrote:
>>
>> Windows has no concept of a default python installation, and I can’t be
>> sure what version of python my users have, if any, so I need to solve 2
>> problems:
>>
>> 1)  Where is python when I’m building?
>>
>> 2)  Where is python when I’m running?
>>
>>
>>
>> To solve #1, I set LLDB_RELOCATABLE_PYTHON to TRUE, and PYTHON_HOME to my
>> python installation (on our buildbots, c:/python351).
>>
>>
>>
>> #2 only needs to be solved if the machine you’re running on doesn’t have
>> the same python installation, in PYTHON_HOME above. To do that, I’ve added
>> code to set a cmake path LLDB_DEFAULT_PYTHONHOME, which I pass as a macro
>> down to InitializePythonHome in
>> source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp, and
>> call Py_SetPythonHome with it. My installations have the python dll and
>> python library directory. We put the library in /lib/python35 and
>> the dll in /bin.
>>
>> --
>>
>> Qualcomm Innovation Center, Inc.
>>
>> The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a
>> Linux Foundation Collaborative Project
>>
>>
>>
>> From: Zachary Turner [mailto:ztur...@google.com]
>> Sent: Wednesday, November 23, 2016 12:40 PM
>> To: Vadim Chugunov <vadi...@gmail.com>
>> Cc: Reid Kleckner <r...@google.com>; Hans Wennborg <h...@chromium.org>;
>> LLDB <lldb-dev@lists.llvm.org>; Ted Woodward <ted.woodw...@codeaurora.org>
>> Subject: Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7
>>
>>
>>
>> I believe the way to fix this is going to be building LLDB for the
>> installer with LLDB_RELOCATABLE_PYTHON=1 at CMake time
>>
>>
>>
>> +Ted, since I believe he is one of the few people currently using this
>> flag.
>>
>> On Wed, Nov 23, 2016 at 10:36 AM Vadim Chugunov <vadi...@gmail.com> wrote:
>>
>> This is still broken in the October snapshot.   Do you know which script
>> is used to build the Windows installer?
>>
>>
>>
>> On Tue, Oct 11, 2016 at 6:24 PM, Zachary Turner <ztur...@google.com>
>> wrote:
>>
>> I think it is a problem with the way we built lldb.  I will look into what
>> additional steps we need to take when making the prebuilt binary so that it
>> works next time.
>>
>>
>>
>> On Tue, Oct 11, 2016 at 6:20 PM Vadim Chugunov <vadi...@gmail.com> wrote:
>>
>> Nope, that didn't help.
>>
>>
>>
>> On Tue, Oct 11, 2016 at 5:16 PM, Zachary Turner <ztur...@google.com>
>> wrote:
>>
>> I may know what this is.  Can you try setting PYTHONPATH though to point
>> to your Python 3.5 installation though and see if it fixes it?  (I don't
>> think it will, but let's try anyway)
>>
>>
>>
>> On Tue, Oct 11, 2016 at 4:59 PM Vadim Chugunov <vadi...@gmail.com> wrote:
>>
>> It outputs 'c:\Program Files (x86)\LLVM\lib\site-packages', however the
>> 'site-packages' directory does not exist.  Nor do I see '_lldb.pyd' anywhere
>> else.
>>
>> 'script import lldb' also fails, of course.
>>
>>
>>
>> On Tue, Oct 11, 2016 at 4:01 PM, Zachary Turner <ztur...@google.com>
>> wrote:
>>
>> He said he did, so I don't know.  Vadim, can you elaborate?  When you run
>> `lldb -P` from the command line, what do you see?
>>
>>
>>
>> On Tue, Oct 11, 2016 at 4:00 PM Reid Kleckner via lldb-dev
>> <lldb-dev@lists.llvm.org> wrote:
>>
>> I imagine that Hans doesn't have Python 3 installed on his system, so LLDB
>> didn't autoconfigure with Python support.
>

Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7

[Zachary Turner via lldb-dev]

So it sounds like you're saying that in order for Python support to work as
part of an LLDB shipped in the installer, we need to do set 3 variables at
CMake time.

1) -DLLDB_RELOCATABLE_PYTHON=TRUE
2) -DPYTHON_HOME = 
3) -DLLDB_DEFAULT_PYTHON_HOME=TRUE

Now because of #3, the lldb shipped in the installer will use the
PYTHONHOME system environment variable to locate python, which must point
to a valid Python 3.5 installation.  Is this correct?

On Mon, Nov 28, 2016 at 9:35 AM Ted Woodward <ted.woodw...@codeaurora.org>
wrote:

> Windows has no concept of a default python installation, and I can’t be
> sure what version of python my users have, if any, so I need to solve 2
> problems:
>
> 1)  Where is python when I’m building?
>
> 2)  Where is python when I’m running?
>
>
>
> To solve #1, I set LLDB_RELOCATABLE_PYTHON to TRUE, and PYTHON_HOME to my
> python installation (on our buildbots, c:/python351).
>
>
>
> #2 only needs to be solved if the machine you’re running on doesn’t have
> the same python installation, in PYTHON_HOME above. To do that, I’ve added
> code to set a cmake path LLDB_DEFAULT_PYTHONHOME, which I pass as a macro
> down to InitializePythonHome in
> source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp, and
> call Py_SetPythonHome with it. My installations have the python dll and
> python library directory. We put the library in /lib/python35 and
> the dll in /bin.
>
> --
>
> Qualcomm Innovation Center, Inc.
>
> The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a
> Linux Foundation Collaborative Project
>
>
>
> *From:* Zachary Turner [mailto:ztur...@google.com]
> *Sent:* Wednesday, November 23, 2016 12:40 PM
> *To:* Vadim Chugunov <vadi...@gmail.com>
> *Cc:* Reid Kleckner <r...@google.com>; Hans Wennborg <h...@chromium.org>;
> LLDB <lldb-dev@lists.llvm.org>; Ted Woodward <ted.woodw...@codeaurora.org>
> *Subject:* Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7
>
>
>
> I believe the way to fix this is going to be building LLDB for the
> installer with LLDB_RELOCATABLE_PYTHON=1 at CMake time
>
>
>
> +Ted, since I believe he is one of the few people currently using this
> flag.
>
> On Wed, Nov 23, 2016 at 10:36 AM Vadim Chugunov <vadi...@gmail.com> wrote:
>
> This is still broken in the October snapshot.   Do you know which script
> is used to build the Windows installer?
>
>
>
> On Tue, Oct 11, 2016 at 6:24 PM, Zachary Turner <ztur...@google.com>
> wrote:
>
> I think it is a problem with the way we built lldb.  I will look into what
> additional steps we need to take when making the prebuilt binary so that it
> works next time.
>
>
>
> On Tue, Oct 11, 2016 at 6:20 PM Vadim Chugunov <vadi...@gmail.com> wrote:
>
> Nope, that didn't help.
>
>
>
> On Tue, Oct 11, 2016 at 5:16 PM, Zachary Turner <ztur...@google.com>
> wrote:
>
> I may know what this is.  Can you try setting PYTHONPATH though to point
> to your Python 3.5 installation though and see if it fixes it?  (I don't
> think it will, but let's try anyway)
>
>
>
> On Tue, Oct 11, 2016 at 4:59 PM Vadim Chugunov <vadi...@gmail.com> wrote:
>
> It outputs 'c:\Program Files (x86)\LLVM\lib\site-packages', however the
> 'site-packages' directory does not exist.  Nor do I see '_lldb.pyd'
> anywhere else.
>
> 'script import lldb' also fails, of course.
>
>
>
> On Tue, Oct 11, 2016 at 4:01 PM, Zachary Turner <ztur...@google.com>
> wrote:
>
> He said he did, so I don't know.  Vadim, can you elaborate?  When you run
> `lldb -P` from the command line, what do you see?
>
>
>
> On Tue, Oct 11, 2016 at 4:00 PM Reid Kleckner via lldb-dev <
> lldb-dev@lists.llvm.org> wrote:
>
> I imagine that Hans doesn't have Python 3 installed on his system, so LLDB
> didn't autoconfigure with Python support.
>
>
>
> On Sun, Oct 9, 2016 at 1:07 PM, Vadim Chugunov via lldb-dev <
> lldb-dev@lists.llvm.org> wrote:
>
> > Does the 4.0 binary not work for you? It is the first release that
> contains prebuilt lldb binary.
>
>
>
> Looks like the Python API is not included though.   Do you know why it was
> left out?
>
>
>
>
> ___
> 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
>
>
>
>
>
>
>
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7

[Vadim Chugunov via lldb-dev]

This is still broken in the October snapshot.   Do you know which script is
used to build the Windows installer?

On Tue, Oct 11, 2016 at 6:24 PM, Zachary Turner  wrote:

> I think it is a problem with the way we built lldb.  I will look into what
> additional steps we need to take when making the prebuilt binary so that it
> works next time.
>
> On Tue, Oct 11, 2016 at 6:20 PM Vadim Chugunov  wrote:
>
>> Nope, that didn't help.
>>
>> On Tue, Oct 11, 2016 at 5:16 PM, Zachary Turner 
>> wrote:
>>
>> I may know what this is.  Can you try setting PYTHONPATH though to point
>> to your Python 3.5 installation though and see if it fixes it?  (I don't
>> think it will, but let's try anyway)
>>
>> On Tue, Oct 11, 2016 at 4:59 PM Vadim Chugunov  wrote:
>>
>> It outputs 'c:\Program Files (x86)\LLVM\lib\site-packages', however the
>> 'site-packages' directory does not exist.  Nor do I see '_lldb.pyd'
>> anywhere else.
>> 'script import lldb' also fails, of course.
>>
>> On Tue, Oct 11, 2016 at 4:01 PM, Zachary Turner 
>> wrote:
>>
>> He said he did, so I don't know.  Vadim, can you elaborate?  When you run
>> `lldb -P` from the command line, what do you see?
>>
>> On Tue, Oct 11, 2016 at 4:00 PM Reid Kleckner via lldb-dev <
>> lldb-dev@lists.llvm.org> wrote:
>>
>> I imagine that Hans doesn't have Python 3 installed on his system, so
>> LLDB didn't autoconfigure with Python support.
>>
>> On Sun, Oct 9, 2016 at 1:07 PM, Vadim Chugunov via lldb-dev <
>> lldb-dev@lists.llvm.org> wrote:
>>
>> > Does the 4.0 binary not work for you? It is the first release that contains
>> prebuilt lldb binary.
>>
>> Looks like the Python API is not included though.   Do you know why it
>> was left out?
>>
>>
>> ___
>> 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
>>
>>
>>
>>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7

[Zachary Turner via lldb-dev]

I think it is a problem with the way we built lldb.  I will look into what
additional steps we need to take when making the prebuilt binary so that it
works next time.

On Tue, Oct 11, 2016 at 6:20 PM Vadim Chugunov  wrote:

> Nope, that didn't help.
>
> On Tue, Oct 11, 2016 at 5:16 PM, Zachary Turner 
> wrote:
>
> I may know what this is.  Can you try setting PYTHONPATH though to point
> to your Python 3.5 installation though and see if it fixes it?  (I don't
> think it will, but let's try anyway)
>
> On Tue, Oct 11, 2016 at 4:59 PM Vadim Chugunov  wrote:
>
> It outputs 'c:\Program Files (x86)\LLVM\lib\site-packages', however the
> 'site-packages' directory does not exist.  Nor do I see '_lldb.pyd'
> anywhere else.
> 'script import lldb' also fails, of course.
>
> On Tue, Oct 11, 2016 at 4:01 PM, Zachary Turner 
> wrote:
>
> He said he did, so I don't know.  Vadim, can you elaborate?  When you run
> `lldb -P` from the command line, what do you see?
>
> On Tue, Oct 11, 2016 at 4:00 PM Reid Kleckner via lldb-dev <
> lldb-dev@lists.llvm.org> wrote:
>
> I imagine that Hans doesn't have Python 3 installed on his system, so LLDB
> didn't autoconfigure with Python support.
>
> On Sun, Oct 9, 2016 at 1:07 PM, Vadim Chugunov via lldb-dev <
> lldb-dev@lists.llvm.org> wrote:
>
> > Does the 4.0 binary not work for you? It is the first release that contains
> prebuilt lldb binary.
>
> Looks like the Python API is not included though.   Do you know why it was
> left out?
>
>
> ___
> 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
>
>
>
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7

[Vadim Chugunov via lldb-dev]

Nope, that didn't help.

On Tue, Oct 11, 2016 at 5:16 PM, Zachary Turner  wrote:

> I may know what this is.  Can you try setting PYTHONPATH though to point
> to your Python 3.5 installation though and see if it fixes it?  (I don't
> think it will, but let's try anyway)
>
> On Tue, Oct 11, 2016 at 4:59 PM Vadim Chugunov  wrote:
>
>> It outputs 'c:\Program Files (x86)\LLVM\lib\site-packages', however the
>> 'site-packages' directory does not exist.  Nor do I see '_lldb.pyd'
>> anywhere else.
>> 'script import lldb' also fails, of course.
>>
>> On Tue, Oct 11, 2016 at 4:01 PM, Zachary Turner 
>> wrote:
>>
>> He said he did, so I don't know.  Vadim, can you elaborate?  When you run
>> `lldb -P` from the command line, what do you see?
>>
>> On Tue, Oct 11, 2016 at 4:00 PM Reid Kleckner via lldb-dev <
>> lldb-dev@lists.llvm.org> wrote:
>>
>> I imagine that Hans doesn't have Python 3 installed on his system, so
>> LLDB didn't autoconfigure with Python support.
>>
>> On Sun, Oct 9, 2016 at 1:07 PM, Vadim Chugunov via lldb-dev <
>> lldb-dev@lists.llvm.org> wrote:
>>
>> > Does the 4.0 binary not work for you? It is the first release that contains
>> prebuilt lldb binary.
>>
>> Looks like the Python API is not included though.   Do you know why it
>> was left out?
>>
>>
>> ___
>> 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
>>
>>
>>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7

[Zachary Turner via lldb-dev]

I may know what this is.  Can you try setting PYTHONPATH though to point to
your Python 3.5 installation though and see if it fixes it?  (I don't think
it will, but let's try anyway)

On Tue, Oct 11, 2016 at 4:59 PM Vadim Chugunov  wrote:

> It outputs 'c:\Program Files (x86)\LLVM\lib\site-packages', however the
> 'site-packages' directory does not exist.  Nor do I see '_lldb.pyd'
> anywhere else.
> 'script import lldb' also fails, of course.
>
> On Tue, Oct 11, 2016 at 4:01 PM, Zachary Turner 
> wrote:
>
> He said he did, so I don't know.  Vadim, can you elaborate?  When you run
> `lldb -P` from the command line, what do you see?
>
> On Tue, Oct 11, 2016 at 4:00 PM Reid Kleckner via lldb-dev <
> lldb-dev@lists.llvm.org> wrote:
>
> I imagine that Hans doesn't have Python 3 installed on his system, so LLDB
> didn't autoconfigure with Python support.
>
> On Sun, Oct 9, 2016 at 1:07 PM, Vadim Chugunov via lldb-dev <
> lldb-dev@lists.llvm.org> wrote:
>
> > Does the 4.0 binary not work for you? It is the first release that contains
> prebuilt lldb binary.
>
> Looks like the Python API is not included though.   Do you know why it was
> left out?
>
>
> ___
> 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
>
>
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7

[Zachary Turner via lldb-dev]

He said he did, so I don't know.  Vadim, can you elaborate?  When you run
`lldb -P` from the command line, what do you see?

On Tue, Oct 11, 2016 at 4:00 PM Reid Kleckner via lldb-dev <
lldb-dev@lists.llvm.org> wrote:

> I imagine that Hans doesn't have Python 3 installed on his system, so LLDB
> didn't autoconfigure with Python support.
>
> On Sun, Oct 9, 2016 at 1:07 PM, Vadim Chugunov via lldb-dev <
> lldb-dev@lists.llvm.org> wrote:
>
> > Does the 4.0 binary not work for you? It is the first release that contains
> prebuilt lldb binary.
>
> Looks like the Python API is not included though.   Do you know why it was
> left out?
>
>
> ___
> 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
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7

[Reid Kleckner via lldb-dev]

I imagine that Hans doesn't have Python 3 installed on his system, so LLDB
didn't autoconfigure with Python support.

On Sun, Oct 9, 2016 at 1:07 PM, Vadim Chugunov via lldb-dev <
lldb-dev@lists.llvm.org> wrote:

> > Does the 4.0 binary not work for you? It is the first release that contains
> prebuilt lldb binary.
>
> Looks like the Python API is not included though.   Do you know why it was
> left out?
>
>
> ___
> 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

Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7

[Vadim Chugunov via lldb-dev]

> Does the 4.0 binary not work for you? It is the first release that contains
prebuilt lldb binary.

Looks like the Python API is not included though.   Do you know why it was
left out?
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7

[Pavel Labath via lldb-dev]

On 22 September 2016 at 04:51, Chunseok Lee via lldb-dev
 wrote:
> Actually, I am trying to remote-debug from lldb(win host) to
> lldb-server(arm/x64 linux). In my case, The problem is that no
> lldb-sever-4.0 is available(I only have lldb-server 3.8 for arm/x64 linux).
> Q) lldb 4.0 and lldb-server 3.8 are compatible each other?

The gdb-remote protocol is generally backward-compatible, but this
isn't a configuration that we are explicitly testing. I think there is
a good chance that it will work, but if it doesn't you're on your own.
:)

pl
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7

[Chunseok Lee via lldb-dev]

Actually, I am trying to remote-debug from lldb(win host) to 
lldb-server(arm/x64 linux). In my case, The problem is that no lldb-sever-4.0 
is available(I only have lldb-server 3.8 for arm/x64 linux). 
Q) lldb 4.0 and lldb-server 3.8 are compatible each other?
Thank you

나의 iPhone에서 보냄

2016. 9. 22. 오후 12:23 Zachary Turner  작성:

> Does the 4.0 binary not work for you?  It is the first release that contains 
> prebuilt lldb binary.  Probably you are one of the first people to test it, 
> so if you encounter problems, let me know what they are.
> 
> The version of windows shouldn't matter as long as you are Win7 or higher.  
> No vista.
> 
>> On Wed, Sep 21, 2016 at 8:22 PM Chunseok Lee via lldb-dev 
>>  wrote:
>> Is there any prebuilt lldb binary for windows7?
>> I tried snapshot llvm binary 3.8, but it does not include lldb. Note that 
>> latest prebuilt(4.0) contains lldb.
>> 
>> 나의 iPhone에서 보냄
>> ___
>> 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

Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7

[Zachary Turner via lldb-dev]

Does the 4.0 binary not work for you?  It is the first release that
contains prebuilt lldb binary.  Probably you are one of the first people to
test it, so if you encounter problems, let me know what they are.

The version of windows shouldn't matter as long as you are Win7 or higher.
No vista.

On Wed, Sep 21, 2016 at 8:22 PM Chunseok Lee via lldb-dev <
lldb-dev@lists.llvm.org> wrote:

> Is there any prebuilt lldb binary for windows7?
> I tried snapshot llvm binary 3.8, but it does not include lldb. Note that
> latest prebuilt(4.0) contains lldb.
>
> 나의 iPhone에서 보냄
> ___
> 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

[lldb-dev] lldb-3.8.1 prebuilt binary for windows7

[Chunseok Lee via lldb-dev]

Is there any prebuilt lldb binary for windows7?
I tried snapshot llvm binary 3.8, but it does not include lldb. Note that 
latest prebuilt(4.0) contains lldb. 

나의 iPhone에서 보냄
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev