tion Collaborative Project
>
>
>
> *From:* Zachary Turner [mailto:ztur...@google.com]
> *Sent:* Monday, January 12, 2015 4:26 PM
> *To:* Ted Woodward; lldb-dev@cs.uiuc.edu
> *Subject:* Re: [lldb-dev] Using Python in LLDB on Windows
>
>
>
> Would this be done by passing th
: Re: [lldb-dev] Using Python in LLDB on Windows
Would this be done by passing the paths you want to add as a command line
option to LLDB?
Is the PYTHONHOME actually needed? The CMake already copies python27.dll to
the output location, so lldb.exe should be able to find it since it's si
Would this be done by passing the paths you want to add as a command line
option to LLDB?
Is the PYTHONHOME actually needed? The CMake already copies python27.dll
to the output location, so lldb.exe should be able to find it since it's
side by side.
On Mon Jan 12 2015 at 2:18:48 PM Ted Woodward
On Windows, there is no notion of a default python installation. A system
may or may not have python installed. And if it did, but was a different
version from the python used to build LLDB, we'd see behavior from warnings
to modules not loading to crashes.
Because of this, LLDB for Hexagon shi
