java.lang.UnsatisfiedLinkError: nativeLoadProlog at Int386w.nativeLoadProlog(Native Method) at Int386w.loadProlog(INT386w.java:28) at FlexIS.loadFlex(FlexIS.java:21) at FlexEG.<init>(FlexEG.java:30) at FlexEG.main(FlexEG.java:18)
That's one way -- works on UNIX variants only. You can also put the libraries on the PATH (works for Windows only). Or you can do things the portable way, and use the special system property for this: it's java.library.path, as in
java -Djava.library.path=c:\wherever Foo
Now, "Kesh", you need to check out our policy on display names, and adjust your accordingly by visiting this page. Thank you kindly!
The java.library.path thing does work fine, as does LD_LIBRARY_PATH on Unix-like platforms. If your program isn't working, then you need to look carefully at what files are where etc. and to read the JNI documentation carefully.
There are other ways to connect Java native methods to their underlying native implementations. Your native code can load the library itself explicitly, using platform-specific code (e.g. LoadLibrary() on Windows). It can then use the JNI RegisterNatives() function to link functions in the library to Java native methods. This also frees you from naming the native functions according to the rather long-winded JNI function names.
Betty Rubble? Well, I would go with Betty... but I'd be thinking of Wilma.
Originally posted by Ernest Friedman-Hill: Or you can do things the portable way, and use the special system property for this: it's java.library.path, as in