[OpenJDK 2D-Dev] Name clash when using the system libjpeg (original) (raw)
Omair Majid omajid at redhat.com
Wed Apr 30 18:52:53 UTC 2014
- Previous message: [OpenJDK 2D-Dev] Name clash when using the system libjpeg
- Next message: [OpenJDK 2D-Dev] Name clash when using the system libjpeg
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
- Phil Race <philip.race at oracle.com> [2014-04-30 14:33]:
The "j2" idea presumably comes from "Java 2" which was a marketing invention for JDK 1.2 in 1998 and has since been purged from all our docs, file names etc etc .. so it would not be my choice. Consider it obsolete / deprecated ..
In another thread, it was pointed out that j2 stands for "Java to". As in "Java to lcms". Anyway, I don't care about the particular naming scheme here. Everything is foreign to me :)
So libjavajpeg.so would be better.
Fantastic!
Presumably libjavajpeg.so would also be just the 'stub' code that via JNI interfaces to the exported interfaces of the system libjpeg ?
Yes, exactly.
If using the system libjpeg, this library would only contain JNI code. It would call into the system libjpeg for actual libjpeg-related functionality.
If using the bundled libjpeg, the bundled libjpeg code gets built and included into libjavajpeg.so too. So both the stub JNI and libjpeg code are included in this libjavajpeg.so.
Either way, there would be no libjpeg.so built. The JDK code will always System.load("javajpeg") which would do the right thing. Does this make sense?
Thanks, Omair
-- PGP Key: 66484681 (http://pgp.mit.edu/) Fingerprint = F072 555B 0A17 3957 4E95 0056 F286 F14F 6648 4681
- Previous message: [OpenJDK 2D-Dev] Name clash when using the system libjpeg
- Next message: [OpenJDK 2D-Dev] Name clash when using the system libjpeg
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]