Andreas

> The FMU imported in OMEdit looks like this: Don't use OMEdit to import FMUs as Modelica code. It's not working 100%. Try OMSimulator or FMPy instead. > Do you...

> Should I trust that if it woks in FMPY it is fine? Most likely. The OMEdit FMU import generates illegal Modelica code and then it complains about it 😆...

@sergiochavezlazo96 Maybe try `libExternalFunc1.dll` instead of `ExternalFunc1.dll`. If that's the issue we can tell CMake to search for libraries without the lib prefix (actually CMake should already do that). How...

I'll take a look and check if I can reproduce the error and then intercept the error with gdb.

longpath is called with an empty wide string `L""` from omc_stat. So `omc_stat` tries to figgure out if a file called `""` exists, and to do so needs the long...

longpath is called with an empty wide string `L""` from omc_stat. So `omc_stat` tries to figgure out if a file called `""` exists, and to do so needs the long...

``` libOpenModelicaRuntimeC.dll!OpenModelica_uriToFilename_impl(threadData_t * threadData, modelica_string uri_om, const char * resourcesDir) (d:\workspace\OM\OpenModelica\OMCompiler\SimulationRuntime\c\util\utility.c:316) libOpenModelicaCompiler.dll!omc_NFEvalFunction_loadLibraryFunction(threadData_t * threadData, modelica_string _libName, modelica_string _fnName, modelica_metatype _extAnnotation, modelica_boolean _debug, modelica_metatype _info) (d:\workspace\OM\OpenModelica\OMCompiler\Compiler\NFFrontEnd\NFEvalFunction.mo:1344) libOpenModelicaCompiler.dll!omc_NFEvalFunction_callExternalFunction(threadData_t * threadData, modelica_string _extName,...