After the Java project was packaged with EXE4J, the results of the other computer operations appeared
Java.lang.UnsatisfiedLinkError:no in Java.library.path's error, just beginning to think that the jar package is not in the Classpath path, later found that Java.library.path and classpath are two different variables, the latter is the class path we know, and the jar package, which is related to the DLL, which specifies DLL file search path.
In my project, with third-party jar packages and DLL files, DLL files are placed in the engineering root directory and running in Eclipse is no problem. But after exe4j packaging, put the DLL file in the same directory as the package generated EXE file, exe run prompt no XXX. JAR in Java.library.path.
Workaround:
In the exe4j packaged Java invocation step, there is an advanced options option under which native libraries is added, adding the directory where the DLL resides.
Java.lang.UnsatisfiedLinkError:no in Java.library.path Solutions