You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There seems to be a bug when trying to run models built on Windows on Linux. A FMU generated from building and then running the example JavaSlave.fmu from an umodified cloned repo on Windows gives a model that runs as expected on Windows but throws the exception:
When run on Linux. Windows and Linux system is configured to use Correto JDK 8.
Strangely models built in wsl Ubuntu 20.04 will run on both Windows and Linux.
Inspecting the generated jar-file and FMU file content reveals that the example folder is present and contains JavaSlave.class and that both the Windows and Linux generated FMUs have exactly the same file size and no obvious differences in content.
This could be a local setup issue but I have verified that the correct Java version is being used while building and that environment variables are set according to README instructions.
The text was updated successfully, but these errors were encountered:
There seems to be a bug when trying to run models built on Windows on Linux. A FMU generated from building and then running the example JavaSlave.fmu from an umodified cloned repo on Windows gives a model that runs as expected on Windows but throws the exception:
java.lang.ClassNotFoundException: example.JavaSlave
When run on Linux. Windows and Linux system is configured to use Correto JDK 8.
Strangely models built in wsl Ubuntu 20.04 will run on both Windows and Linux.
Inspecting the generated jar-file and FMU file content reveals that the
example
folder is present and containsJavaSlave.class
and that both the Windows and Linux generated FMUs have exactly the same file size and no obvious differences in content.This could be a local setup issue but I have verified that the correct Java version is being used while building and that environment variables are set according to README instructions.
The text was updated successfully, but these errors were encountered: