Question about JDK-8024281 Mac OS X: stop relying on Apple's JavaVM Frameworks

[Michael Hall]

On Feb 20, 2015, at 12:05 PM, Hendrik Schreiber <hs at tagtraum.com> wrote:

>>> 
>>> Follow-up question here: I'm trying to use autoconf to identify the
>>> location of the proper include directories and libraries for subsequent
>>> use of libtool to create a .libjni JNI dynamic library.
>> 
>> You should be using .dylib for JNI libs these days.
> 
> Please excuse my ignorance, but
> 
> Why?
> And what's the difference?

If I remember right at one point during the port, jnilib was broken at least for some functionality. I bug reported and the ‘legacy’ behavior was restored. 
It is a little strange. Java tends to deprecate a lot but doesn't actually break backward compatibility very often.
I’m not sure what the deprecation reasoning would be either. Maybe just to eliminate java having a unique special case file extension for something the platform already has it’s own extensions for. If the jnilib executable itself isn’t cross-platform, like a native lib compiled on OS X won’t run on Windows, then having a cross-platform file extension maybe doesn’t make sense either.

Michael Hall

trz nio.2 for OS X http://www195.pair.com/mik3hall/index.html#trz

HalfPipe Java 6/7 shell app http://www195.pair.com/mik3hall/index.html#halfpipe

AppConverter convert Apple jvm to openjdk apps http://www195.pair.com/mik3hall/index.html#appconverter