Youssef wrote:
>Now, 'file' command tell me that all *.dylib in usr/lib/java (par
>consequent,libObjCJava)gives this output.
>
>>file /usr/lib/java/libObjCJava.A.dylib
>/usr/lib/java/libObjCJava.A.dylib: Mach-O universal binary with 2
>architectures
>/usr/lib/java/libObjCJava.A.dylib (for architecture i386): Mach-O
>dynamically linked shared library i386
>/usr/lib/java/libObjCJava.A.dylib (for architecture ppc7400): Mach-O
>dynamically linked shared library ppc
Why do you need to link to libObjCJava.A.dylib?
Or why do you think you need to?
>does this means that I cannot use thoses dylib anywhere in my machine to
>call Obj-C app?
Please explain what you mean by "call Obj-C app", and why you think
libObjCJava.A.dylib is necessary to do it.
We need a better description of what you're trying to accomplish. So far,
the only description you've given is for a JNI lib called by a Java class.
Suddenly libObjCJava.A.dylib seems to be necessary, even though it wasn't
necessary for the JNI-lib you were using before. Overall, you haven't said
what you're building, how it uses Objective-C, where you got the source
from, or what you're trying to do.
-- GG
_______________________________________________
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
This email sent to email@hidden
