[LLVMdev] Python bindings
Eric van Riet Paap
eric at vanrietpaap.nl
Thu Apr 20 17:51:35 PDT 2006
Thank you for this mail. Personally I think the fact that is not
stable yet is even more reason to put it in to CVS somewhere.
The file that you attached here and that you have send me is the one
I forwarded to Pertti. My vote would be to not put it
into the LLVM cvs actually but in a seperate repository so it would
be easier to assign commit-rights to developers.
But maybe the commit-rights could be set even to this specific llvm
subproject on a per user basis, so you, Pertti and I could
commit to the bindings only, which would maybe be even better.
On Apr 21, 2006, at 3:55 AM, Jarno Seppänen wrote:
> 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.
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
More information about the llvm-dev