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

Zachary Turner zturner at google.com
Wed Feb 25 09:46:35 PST 2015


On Wed, Feb 25, 2015 at 9:39 AM Ted Woodward <ted.woodward at codeaurora.org>
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 too.  As it's the only way to run tests.  I think his
point is just that it's a big barrier to entry.  I've got 3 guys who sit
around me.  One works on the windows linker, and the other two are
responsible for much of clang-cl.  None of them feel like going through
these hoops to build LLDB, even though there's bugs in LLDB on Windows that
their expertise would be a great asset in making some progress on.

I mean yes I could do it for them, and yes they could ultimately do it
themselves, but the point is that it shouldn't be this difficult.  What
about people without the same amount of technical background, but who still
want to hack around on the debugger?  I dont' want to discourage anyone
from being able to work on the project.  Barriers close doors. I want the
doors to be open.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20150225/3d1f2347/attachment.html>


More information about the lldb-dev mailing list