On 2 July 2013 16:16, Jason Molenda <[email protected]> wrote: > On Jul 2, 2013, at 10:18 AM, Ed Maste <[email protected]> wrote: > >> Incidentally, I'm curious about how widely used LLDB_DISABLE_PYTHON >> is. For FreeBSD we'd eventually like to bring lldb into the base >> system, so having it be usable without Python is very interesting to >> us. > > As Greg said, we are actively using the Python-less build of lldb in one > configuration at Apple so it should build and work fine, I'm a little > surprised that the build failure you hit didn't affect our build. > > > One thing to think about is that lldb users typically adopt the python > scripting interfaces and build up collections of custom commands/formatters. > For new lldb users, lack of Python is not important - but once people have > grown familiar with its capabilities, the lack of Python will be a real drag > for them.
I agree, but this is only for our base system; in the worst case the user can just install (a second copy of) lldb from a package or the ports tree, and it will bring along Python. Ideally though I'd like to be able to build with Python support but have it handle a missing python .so at runtime, so that the user can later install Python and have it "just work." _______________________________________________ lldb-dev mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
