I don't think the lib is being linked right. I have a JNI lib that
uses JAWT successfully, and it does not have a direct dependency on
libjawt.dylib (as reported by otool -L), only a dependency on the
JavaVM framework proper. The source code only names a call to
JAWT_GetAWT -- all other JAWT calls are indirect via a function
table filled in by GetAWT, and need not be made known to the
linker. JAWT-GetAWT is in the JavaVM framework. Looking at
libjawt.dylib I only see functions that are defined in the function
table, so it need not be included in the link. Getting addresses of
the functions to be placed in the function table becomes the JVM's
responsibility at runtime. I don't see a dependency from the
framework to libjawt.dylib, so it must either be statically linked,
or using some funky mechanism that is not apparent to the causal
observer.
So it may be that JNA just needs to drop the explicit -ljawt in order
to be properly linked, since it is already linking to the JavaVM
framework.
FYI my makefile places no -l terms in the link statement, only -
framework terms:
We have different SDK requirements for PPC and x86 jnilibs, hence
the architecture-specific builds with different tool sets (one for
ppc w/GCC 3 and one for x86 w/GCC 4).
The original poster was trying to build JNA with OSX 10.3
compatibility (which is only for PPC, right?).
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
