[Lldb-commits] [PATCH] D11431: Convert ScriptInterpreters to being first-class plugins

[Zachary Turner]

zturner added a comment.

Hi Greg,

I wonder if this has something to do with the fact that the SWIG generation shell script is one of the build phases of LLDB.Framework as you mentioned once before here: http://lists.cs.uiuc.edu/pipermail/lldb-dev/2015-February/006685.html.  Is it possible to change this so that the SWIG wrappers are built along with the regular source?  It seems to me like LLDBWrapPython.cpp should be compiled into Plugins/ScriptInterpreter/Python

Or, alternatively, manually fiddle with the linker line as a last resort?  This might be a better approach for now, because moving the location of LLDBWrapPython.cpp might require changes to the shells cript and python script.  Which we can do, but it seems better as a followup CL just so that we can do things in small pieces in order to keep moving forward.

I'm still a little unclear why the problem happens though.  If LLDBWrapPython.cpp is being linked into liblldb, and ScriptInterpreterPython is being built as a static library, then where are the linker errors coming from?  They're declared extern in the Python plugin, which shouldn't care that they're not visible at link time, because liblldb contains all the definitions.  What part am I missing?


http://reviews.llvm.org/D11431