Hi Andreas, On Tue, 2005-08-02 at 06:41 +0200, Andreas Tobler wrote: > Well, here I should have said 'once', with the actual cp I didn't. :( > But I know jamvm will fail because it in src/dll.c:300 it checks against > .so and new will .dylib on darwin.
OK. Useful additional datapoint :) Maybe the simplest solution then would be to symlink the .dylib to a .so with the same name as an additional workaround for darwin based systems. I looked a bit around and also found the extension .jnilib used on darwin systems for libraries loaded through jni. There is a patch for libtool to add a -jnimodule option, but I don't believe that has been integrated. http://lists.gnu.org/archive/html/libtool/2002-07/msg00010.html Chris had a fight around this same issue for our libxmlj: http://lists.gnu.org/archive/html/classpath/2004-07/msg00207.html It seems it is all a bit of a maze of extensions and options I am afraid :( Cheers, Mark -- Escape the Java Trap with GNU Classpath! http://www.gnu.org/philosophy/java-trap.html Join the community at http://planet.classpath.org/
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Classpath-patches mailing list Classpath-patches@gnu.org http://lists.gnu.org/mailman/listinfo/classpath-patches
