7 messages in org.openoffice.porting.devRe: [porting-dev] what is the differe...
FromSent OnAttachments
Kevin.HendricksJan 7, 2004 7:55 am 
Dan WilliamsJan 7, 2004 8:05 am 
Patrick LubyJan 7, 2004 8:16 am 
Greg ParkerJan 8, 2004 1:22 pm 
Kay Ramme - Sun Germany - HamburgJan 9, 2004 12:01 am 
Sander VesikJan 9, 2004 6:11 am 
Greg ParkerJan 9, 2004 11:51 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [porting-dev] what is the difference between a jnilib and a dylib and when is each needed?Actions
From:Greg Parker (gpar@sealiesoftware.com)
Date:Jan 8, 2004 1:22:02 pm
List:org.openoffice.porting.dev

Patrick Luby writes:

For some reason, Apple decided that "jnilib" would be the magic file extension that they would serach for when you invoke System.loadLibrary(). Who know why they didn't use *.dylib. No matter, you can use a *.dylib and make a *.jnilib softlink to it and Java won't complain.

Historically, thre was a good reason. In Mac OS X 10.0 days, libraries with implementations of Java native code were required to be Mach-O bundles because of a dyld limitation. They could not be Mach-O shared libraries (i.e. .dylibs).

The dyld limitation was removed in Mac OS X 10.1, I think. Now libraries with implementations of Java native code may be Mach-O shared libraries. The .jnilib extension lives on. Currently it means little, except the Java library loading methods look for .jnilib files. Making a symlink of .jnilib -> .dylib should work fine.

-- Greg Parker gpar@sealiesoftware.com

--------------------------------------------------------------------- To unsubscribe, e-mail: dev-@porting.openoffice.org For additional commands, e-mail: dev-@porting.openoffice.org