Re: Status of Swig Java bindings on Mac OS X?

Hi,

Afaik, they do not work. I might be terribly wrong, since I haven't
actually watched the code in quite a while. I had the intention of
bringing the swig-java-bindings up to speed earlier, and talked a lot
with daniell rall about it.

allthough, I've been busy, and I haven't seen a single post to the
mailing list from dlr in quite a while, so I suspect that he hasn't done
anything with it lately either.

>
> Shouldn't that be '-framework JavaVM' instead of '-framework Python'?
>

sounds reasonable yes.

>
> Also, on Mac OS X the built JNI library has to be named something like
> 'libLIBNAME.jnilib' but they are built as e.g. _wc.so at the moment
>

yep, the problem is the same on *nix, since the files need to be named
libLIBNAME.so to work.

>
> Now the questions:
>
> 1. Is it possible to build the swig java bindings from the 1.0.4
> tarball on Mac OS X at the moment? Has anybody tried this before?
>

seriously doubt it..

> 2. Is it possible on trunk?
>

seriously doubt it..

> 3. If not, is anybody working on making swig java bindings usable on
> Mac OS X?
>

I was working on making it work in *nix, and so was dlr, but I've been
very busy lately, and I suspect he has as well.

I had the swig bindings compiling on my computer, but on the other hand
very little was actually implemented on the swig bindings, and I suspect
that this is still the case.

allthough, as stated in the beginning, I might be completely wrong here,
since it was quite a while since I did anything.

cheers,
!g

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon May 24 18:47:35 2004