Eric van Riet Paap wrote:> The boost Python are not (yet) part of LLVM so I suppose it would make > most sense to try to makes fixes/changes so they would work for 1.7 and > then try to get them into LLVM CVS.I tried compiling the bindings, and it seems that it would not be too much work to compile them for 1.7. I'm not familiar enough with LLVM to assess how complete the bindings are. Boost.Python does not handle void* directly, so any methods with void* arguments or return values need a little bit of extra attention. Otherwise I don't foresee any great difficulties.> It would be good in such a case to > ask the author of the bindings again if he would allow this, because > basicaly I think he has to agree to the LLVM lincense.I don't think this will be a problem, since README.txt already mentions the LLVM license... In my opinion, the most sensible thing to do with the bindings right now would be to put them up on a CVS server somewhere. Is there a chance of getting them at uiuc as a separate tree? Another alternative would be to use SourceForge or something similar. If our group decides to go with LLVM, then I'd be happy to work on the bindings, but that choice is not entirely up to me. -- Pertti
Hi, here's a brief update of the status of the python bindings. Recently I've updated them with the API changes in LLVM 1.6 and split the submodules (VMCore, ExecutionEngine, etc.) into separate builds, making the dynamic libraries smaller. I agree that the bindings should be in a CVS somewhere, and last year there was some discussion of putting them in the llvm tree. The python bindings are otherwise ready for the "projects" folder, and I decided to change the license and assign copyright to UIUC for this to happen, but there are persistent (linkage related?) crashes I haven't had the time to solve so far. Also, I have quite little time for this, so things have not exactly been flying forward :) So, here attached is the latest package I sent to Eric last month. Cheers, Jarno -------------- next part -------------- A non-text attachment was scrubbed... Name: python-llvm-2006-03-23.zip.bin Type: application/octet-stream Size: 154949 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20060420/583919a3/attachment.bin>