[lldb-dev] static swig bindings and xcode workspace

[Zachary Turner via lldb-dev]

Has the xcode build been changed to use static bindings yet?  I got to
thinking that maybe it would make sense to put them alongside the xcode
workspace folders, just to emphasize that the static bindings were an
artifact of how the xcode build works.  This way we just say "Xcode build
uses static bindings" and "CMake build needs an installed swig", and this
is enforced at the directory level.

In order to do this you'd have to probably make a new toplevel folder to
house both the lldb.xcodeproj and lldb.xcworkspace folders, but I think
that would be useful for other reasons as well.  For example, I want to
check in a visual studio python solution for the test suite at some point,
and it would make sense if all of this additional stuff was in one place.
So perhaps something like:

lldb
|__ contrib
    |__ xcode
        |__ LLDBWrapPython.cpp
        |__ lldb.py
        |__ lldb.xcodeproj
        |__ lldb.xcworkspace
    |__ msvc

I have been thinking about this idea of a contrib folder for a while
anyway, but wanted to have more reasons to make use of it before I brought
it up.

Good idea?  Bad idea?  Thoughts?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20151130/e6f6cf31/attachment.html>