That sounds really weird. XCode used to take care of it (somehow) if
one would simply add the JNI to the classpath, and tell XCode to
merge it into the application jar. Now, I can't imagine XCode being
Java-smart enough to actually do what you describe because it detects
that one of the added classpath items is a JNI file.
It does however explain why the JNI is not simply bundled with the
Quaqua jar distribution...
Darn, this is becoming troublesome. I've been putting it off because
I assumed it would be simple :)
Thanks for the info,
F
On Mar 04, 2008, at 13:18, Mike Schrag wrote:
Not without some magic (and this isn't an Eclipse thing, this is
just a Java thing) ... As part of your startup, you have to read
the JNI file out of the jar and write it to the filesystem and then
load that library.
Oh well, I suppose I'll have to do it that way.
This is what Eclipse does, for instance, with SWT. I don't know of
any way for System.loadLibrary to load a JNI lib out of a jar file
directly.
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
