I was able to build successfully with no changes to your patch Eli. I did have to install the dev packages for python 2.6 and editline (version 1) main things you need to intall:
python2.6-dev libghc6-editline-dev On Jul 6, 2010, at 10:07 AM, Eli Friedman wrote: > On Tue, Jul 6, 2010 at 8:47 AM, Greg Clayton <[email protected]> wrote: >> >> On Jul 3, 2010, at 7:09 PM, Eli Friedman wrote: >> >>> On Fri, Jul 2, 2010 at 6:10 PM, Sean Callanan <[email protected]> wrote: >>>> Eli, >>>> the generated file you're looking for is LLDB_vers.c, a file generated by >>>> Apple Generic Versioning, which is described in more detail >>>> here: >>>> http://developer.apple.com/mac/library/documentation/Darwin/Reference/ManPages/man8/agvtool.8.html. >>>> A properly-built LLDB_vers.c looks like this: >>>> – >>>> const unsigned char LLDBVersionString[] __attribute__ ((used)) = >>>> "@(#)PROGRAM:LLDB PROJECT:lldb-24" "\n"; const double LLDBVersionNumber >>>> __attribute__ ((used)) = (double)24.; >>>> – >>>> I've attached a simple Perl script that generates the above code given the >>>> location of the .pbxproj as input. >>> >>> Cool, thanks; I didn't realize that was missing. I've managed to >>> integrate it in (but I'm not attaching a patch yet; see below). >>> >>> The other thing that is missing is generating the SWIG bindings; see >>> http://lists.cs.uiuc.edu/pipermail/lldb-dev/2010-June/000045.html . >>> I've managed to get it mostly working, but I'm running into an issue >>> with circular dependencies: bindings -> source/API -> >>> source/Interpreter -> bindings. I'm not sure how to go about dealing >>> with this... I'm tempted to just collapse lldb into a single .a file, >>> but I don't know how to tell the LLVM Makefile system to do that. Any >>> ideas? >> >> Is this a header file include issue? All files in "include/lldb/API" should >> only be pulling in stuff from "lldb/API/*.h" and from "lldb/lldb-*.h". >> >> I will try and build this on my Ubuntu install and see if I can recognize >> anything. Can you send me a patch with your SWIG changes in? I can then >> check it out and let you know what I find. > > Version with the additional fixes attached. The issue is if I try to > get rid of the hacks in source/Interpreter/ScriptInterpreterPython.cpp > , there isn't any possible ordering of libraries that will make > everything link successfully. > > -Eli > <lldb.txt> _______________________________________________ lldb-dev mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
