Native library support exists in the current next release or
CVS head. It's worked for me on linux and windows. IIRC
netx extracts the native libraries to a temp folder (where
the JARs are cached). You can even use the same native
library from multiple JNLP applications running in the same
JVM (although at some waste since the dll/so is loaded twice).
Native libraries may only work from the .jnlp file that
loaded them (ie if multiple jnlp files are referred to by
the main file, the code using the native lib must be in the
same jnlp file as the native code). This can't really be
helped right now due to how the classloaders are defined,
due to legacy support for ocd / pod desktop components.
Native libraries haven't been tested on osx.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=250242
Native library support exists in the current next release or
CVS head. It's worked for me on linux and windows. IIRC
netx extracts the native libraries to a temp folder (where
the JARs are cached). You can even use the same native
library from multiple JNLP applications running in the same
JVM (although at some waste since the dll/so is loaded twice).
Native libraries may only work from the .jnlp file that
loaded them (ie if multiple jnlp files are referred to by
the main file, the code using the native lib must be in the
same jnlp file as the native code). This can't really be
helped right now due to how the classloaders are defined,
due to legacy support for ocd / pod desktop components.
Native libraries haven't been tested on osx.