[Lldb-commits] [PATCH] The great Python split

[jingham at apple.com]

If it is a target, for sure, that's easy.  Actually you could do it with a project but that's unnecessary.  And Xcode has targets that build libraries, rather than having libraries as first-class objects...

Jim

> On Feb 27, 2015, at 1:22 PM, Zachary Turner <zturner at google.com> wrote:
> 
> Can the Xcode project set up a dependency between the entire ScriptInterpreterPython project (or target, or library, I'm not sure what the right term is in Xcode parlance) to the API library?  Nothing else Python-related makes sense to compile either if you haven't built API.
> 
> On Fri, Feb 27, 2015 at 1:16 PM Greg Clayton <clayborg at gmail.com> wrote:
> So we can make this work if we shuffle things around such that ScriptInterpreterPython.cpp is only built if the "lldb/source//API" stuff is built and we can make LLDBWrapPython.cpp is only created along with the files in "lldb/source/API/ScriptInterpreter/Python"?
> 
> 
> http://reviews.llvm.org/D7946
> 
> EMAIL PREFERENCES
>   http://reviews.llvm.org/settings/panel/emailpreferences/
> 
> 
> _______________________________________________
> lldb-commits mailing list
> lldb-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-commits