Just as an aside: One general problem with native dependencies is that java.library.path only applies to direct dependencies from Java to native libraries, but not to transitive dependencies, that is from one ntaive lirary to another. If a native library is loaded by Java, and this library has a dependency to another native library, this second library is not loaded by Java, but natively by the OS, and hence ignores any java.library.path settings. This is a typical situation when the first library is a JNI bridge library to an existing native library. In that case OS specific mechanisms have to be used so that the dependent native libraries can be correctly located.
-- Niklas Matthies
