UnsatisfiedLinkError When Running Java Examples

[mullerj]

I am attempting to run the Java examples on Windows, but I am having a problem loading the libraries.
I used the Python waf tool to build the Java extension with x64 target:
python waf configure --build-java --msvc_target=x64
python waf
Successfully built and files were output to build directory.
Ran the command to build the Java examples and included norm.jar from the build directory in the class path:
javac -cp ../../build/norm.jar *.java
Successfully built the examples.
Attempted to run the NormStreamSend example from the root Norm directory using the build directory:
java -Djava.library.path=.\build -cp .\examples\java;.\build\norm.jar NormStreamSend
Received java.lang.UnsatisfiedLinkError on mil_navy_nrl_norm:

Exception in thread "main" java.lang.UnsatisfiedLinkError: no mil_navy_nrl_norm in java.library.path: .\build
        at java.base/java.lang.ClassLoader.loadLibrary(ClassLoader.java:2444)
        at java.base/java.lang.Runtime.loadLibrary0(Runtime.java:848)
        at java.base/java.lang.System.loadLibrary(System.java:2047)
        at mil.navy.nrl.norm.NormInstance.<clinit>(NormInstance.java:19)        at NormStreamSend.main(NormStreamSend.java:38)

The mil_navy_nrl_norm files are in the build directory, but the dll has a -1 at the end of the filename:

If I copy mil_navy_nrl_norm-1.dll and rename as mil_navy_nrl_norm.dll, it seems to find mil_navy_nrl_norm-1.dll, but is unable to find dependent libraries.

Attempted to run the example again:
java -Djava.library.path=.\build -cp .\examples\java;.\build\norm.jar NormStreamSend
Received a different error about the dependent libraries:

Exception in thread "main" java.lang.UnsatisfiedLinkError: C:\projects\norm\build\mil_navy_nrl_norm.dll: Can't find dependent libraries
        at java.base/jdk.internal.loader.NativeLibraries.load(Native Method)
        at java.base/jdk.internal.loader.NativeLibraries$NativeLibraryImpl.open(NativeLibraries.java:331)
        at java.base/jdk.internal.loader.NativeLibraries.loadLibrary(NativeLibraries.java:197)
        at java.base/jdk.internal.loader.NativeLibraries.loadLibrary(NativeLibraries.java:139)
        at java.base/jdk.internal.loader.NativeLibraries.findFromPaths(NativeLibraries.java:259)
        at java.base/jdk.internal.loader.NativeLibraries.loadLibrary(NativeLibraries.java:251)
        at java.base/java.lang.ClassLoader.loadLibrary(ClassLoader.java:2437)
        at java.base/java.lang.Runtime.loadLibrary0(Runtime.java:848)
        at java.base/java.lang.System.loadLibrary(System.java:2047)
        at mil.navy.nrl.norm.NormInstance.<clinit>(NormInstance.java:19)
        at NormStreamSend.main(NormStreamSend.java:38)

I noticed that the Norm dll also has a -1 at the end of the filename.

I tried copying the Norm dll and removing -1 from the name, but it does not help.

Any suggestions on running the Java examples on Windows?

[mullerj]

I missed the step in README-Java.txt to set the path when running on Windows:
set PATH=%PATH%;<path to mil_navy_nrl_norm.dll>
Once I set the path, I was able to run the Java examples.

[mullerj]

Still having the problem with -1 in the dll filenames. Once the dll filenames are corrected, the examples work. Used a GitHub codespace, which is Linux, and did not have any problems with the library filenames. Is anybody else having the same problem with the dll filenames on Windows?

[bebopagogo]

The wscript sets the "vnum" (version number) when building a library. On Unix systems this creates the basic libnorm.so shared libarry and symbolic links to that shared library files with the version numbering. On Windows, perhaps that's a problem (where does "./waf install" put files on Windows? And does the install rename anything? Perhaps the solution is to change the line that passes the vnum into the shared library build command in the wscript to:

vnum == VERSION if 'windows' != system else None

I need to read up on how library versioning is done on Windows. Since I recently switched to an ARM-based MacBook for daily use, my Windows VM I use for build and test is not readily available to me. I will check into this when I can.