Re: [lldb-dev] RFC: Separation of embedded Python from the rest of LLDB.

Hello, On Wed, 25 Feb 2015 04:56:00 + Zachary Turner wrote: > A little background: The single biggest painpoint for working with LLDB on > Windows currently is Python. There is a long > > documented

Re: [lldb-dev] RFC: Separation of embedded Python from the rest of LLDB.

Most Python stuff is in ScriptInterpreterPython (see Include/Utility/PythonPointer.h for an example of code that isn't). But ScriptInterpreterPython is just compiled straight into Interpreter, instead of into its own library. That's the part that isn't working. If someone wants to add support fo

Re: [lldb-dev] RFC: Separation of embedded Python from the rest of LLDB.

We had planned on python being able to be replaced by another language and abstracted all python stuff into the pure virtual ScriptInterpreter and the one and only scripting subclass ScriptInterpreterPython. What part of this abstraction isn't working for people? I don't see the need for heroic

Re: [lldb-dev] RFC: Separation of embedded Python from the rest of LLDB.

aborative Project > > > > *From:* Zachary Turner [mailto:ztur...@google.com] > *Sent:* Wednesday, February 25, 2015 12:35 PM > > > *To:* Ted Woodward; Reid Kleckner; Vince Harron > *Cc:* lldb-dev@cs.uiuc.edu > *Subject:* Re: [lldb-dev] RFC: Separation of embedded Pytho

Re: [lldb-dev] RFC: Separation of embedded Python from the rest of LLDB.

: Zachary Turner [mailto:ztur...@google.com] Sent: Wednesday, February 25, 2015 11:47 AM To: Ted Woodward; Reid Kleckner; Vince Harron Cc: lldb-dev@cs.uiuc.edu Subject: Re: [lldb-dev] RFC: Separation of embedded Python from the rest of LLDB. On Wed, Feb 25, 2015 at 9:39 AM Ted Woodward

Re: [lldb-dev] RFC: Separation of embedded Python from the rest of LLDB.

On Wed, Feb 25, 2015 at 9:39 AM Ted Woodward wrote: > > Saying you can’t build Python with VS2013 isn’t true. I did. I’m having > issues with some of the bindings (specifically “print lldb.debugger” gives > “No value”, even though it’s there), but for the most part it works. > Well sure, I did to

Re: [lldb-dev] RFC: Separation of embedded Python from the rest of LLDB.

On Wed, Feb 25, 2015 at 5:58 AM, Vince Harron wrote: > This seems like a lot of work to support Windows users who might want to > use pre-compiled python modules. > To me, the primary benefit is that you can build LLDB with Python support without building Python from source. More onerous, once y

Re: [lldb-dev] RFC: Separation of embedded Python from the rest of LLDB.

IANAL, but I floated this idea once and people weren't super thrilled about the idea of checking in binaries or headers. That reminds me though that I should ask again. It also doesn't solve the problem for users of lldb on windows who need support for using other extension modules in their script

Re: [lldb-dev] RFC: Separation of embedded Python from the rest of LLDB.

ersions of python.-Duane. Original Message -------- Subject: Re: [lldb-dev] RFC: Separation of embedded Python from the rest of LLDB. From: Zachary Turner <ztur...@google.com> Date: Wed, February 25, 2015 11:47 am To: Greg Clayton <gclay...@apple.com> Cc: "lldb-dev@cs.uiuc

Re: [lldb-dev] RFC: Separation of embedded Python from the rest of LLDB.

Sorry, hit send too soon. The big thing that will change is people who do: #include "lldb-python.h" and #if !defined(LLDB_DISABLE_PYTHON) There are currently a lot of instances of this in the code. The path forward for this would be to gradually change #if defined(LLDB_DISABLE_PYTHON) to simp

Re: [lldb-dev] RFC: Separation of embedded Python from the rest of LLDB.

Also, I don't think the fixups necessary for out of tree code associated with separating the library will be anything larger than what would need to be done for someone adding another language anyway. Some header and source files will move around, and the build dependency structure will change. Th

Re: [lldb-dev] RFC: Separation of embedded Python from the rest of LLDB.

: Wednesday, February 25, 2015 12:35 PM To: Ted Woodward; Reid Kleckner; Vince Harron Cc: lldb-dev@cs.uiuc.edu Subject: Re: [lldb-dev] RFC: Separation of embedded Python from the rest of LLDB. Just to be clear, with solution #1 proposed in the original message, then your option #3 is guaranteed

Re: [lldb-dev] RFC: Separation of embedded Python from the rest of LLDB.

t; 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, February 25, 2015 11:47 AM > *To:* Ted Wo

Re: [lldb-dev] RFC: Separation of embedded Python from the rest of LLDB.

oun...@cs.uiuc.edu] On Behalf Of Reid Kleckner Sent: Wednesday, February 25, 2015 10:59 AM To: Vince Harron Cc: lldb-dev@cs.uiuc.edu Subject: Re: [lldb-dev] RFC: Separation of embedded Python from the rest of LLDB. On Wed, Feb 25, 2015 at 5:58 AM, Vince Harron mailto:vhar...@google.com> &

Re: [lldb-dev] RFC: Separation of embedded Python from the rest of LLDB.

I agree with you for the most part, including that the code separation has the lowest impact. But it's worth mentioning that here, EOL for VC++ 2008 is 2018 . So while techni

Re: [lldb-dev] RFC: Separation of embedded Python from the rest of LLDB.

I'd like to also add my support to solution #1. My use case is literally what Zachary has outlined -- Building on Windows, wanting to interface with LLDB not using Python but a different language, say C#. The Python requirement (and that too building from source) was a bit of an odd (for a non-Py

Re: [lldb-dev] RFC: Separation of embedded Python from the rest of LLDB.

This seems like a lot of work to support Windows users who might want to use pre-compiled python modules. I think we should distribute a VS2015 based version of Python 2.7 binaries and call it a day. We can worry about 2020 problems in 2020. =) Reasonable people may disagree. On Tue, Feb 24,