[lldb-dev] Current status of my Linux porting

[Caroline Tice]

On Jun 10, 2010, at 12:21 AM, Eli Friedman wrote:

> On Wed, Jun 9, 2010 at 11:18 PM, Greg Clayton <gclayton at apple.com> wrote:
> 
>> source/Interpreter/ScriptInterpreterPython.cpp:
>> My build doesn't define init_lldb anywhere; I have no idea where the
>> definition is supposed to be.
>> 
>> This comes from the file cpp file that is generated by swig when run on the
>> ABI sources.
>> This is done by a shell script build phaes in the Xcode project that
>> essentially does a:
>> cd scripts
>> sh ./build-swig-wrapper-classes.sh lldb.swig ../source/LLDBWrapPython.cpp
>> The init_lldb ends up being in the LLDBWrapPython.cpp
> 
> Ah, okay; I'll adjust my in-progress build system to do that.
> 


There are a couple of  things to be aware of in running those scripts.  The first thing is that,
as written, they were intended to be run from Xcode, which means they contain references to
environment variables that Xcode defines in its build process, so they probably won't work for
you 'as is'.    One of the next things on my to do list is to try to modify the scripts to take those
values as parameters instead.  The other thing you should be aware of is that there are two sets of
scripts, the build-swig-... scripts and the finish-swig-... scripts.  The build scripts need to be run fairly early
in the overall build process, because they cause SWIG to build the C++ file(s) for the scripting language API(s) that need to be compiled and linked with all the other source files to create lldb.  The finish-swig... scripts
need to be run after it's all been compiled, to generate links and copy files around to where they need to be
in order for the embedded scripting stuff in lldb to find them properly. 

-- Caroline
ctice at apple.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20100610/4a5ca465/attachment.html>