krytarowski added a comment. I dislike delegating jobs (or hiding problems) of CMake (assuming that autoconf/gmake is already dead) to external scripts like Python ones.
In the goal, I plan to add LLDB in the NetBSD base (next to LLVM and Clang) where there is no Python at all. In FreeBSD there is no Python in base as well. To state it stronger, there might never be Python in the base. I would expect to just have a single switch like `-DLLDB_ENABLE_PYTHON`, while I don't understand `-DLLDB_ALLOW_STATIC_BINDINGS`. When I will catch up with platform support I'm considering to prepare bindings in Lua, as this is the standard scripting language in NetBSD (we script with it kernel, packet filter, userland etc). Lua offers native C/C++ bindings (as there is no need for intermediate tool) by design and is a dynamic language close to Python. But this isn't plan for this year. For now please leave an option that end user to disable Python. Otherwise erasing it will be done downstream without benefit for the project. http://reviews.llvm.org/D14790 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
