-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
25 - ctest_fmi2_import_default_experiment_test (Failed) #8
Comments
Hi! The test failure is not expected. For MinGW we're testing with GCC-TDM (GCC 5.1).
|
Thank you for the swift reply, Filip! First, I compiled with GNU GCC-9.2.0-2 from the standard MinGW packages. Now, I tried with GCC-TDM 9.2.0, and it worked.
Best wishes, . |
Ah, no! It's not all, actually. In the next step, I've tried to install PyFMI-2.5 However, I got the following error: I compared win32 binaries from https://jmodelica.org/FMILibrary/FMILibrary-2.0-win32.zip with mine, and it turns out that the files don't have proper names: So I renamed libfmilib_shared.dll to fmilib_shared.dll and libfmilib_shared.dll.a to libfmilib_shared.lib and the installation of PyFMI went smoothly. At the end, python-3.8.3 doesn't want to load pyfmi module: No idea how to fix this. Best wishes, |
…or_release Prepare for release
Hello, everyone!
I've compiled 2.2.3 version of the library on Windows 10 with the help of the latest version of MinGW and MSYS.
mkdir mybuild
cd mybuild
cmake-gui ..
The only option I changed in configuration was:
FMILIB_FMI_PLATFORM I set to win64 instead of win32
source code dir: fmi-library-master
binaries dir: fmi-library-master/mybuild
Then I did:
make
make install
make test
During the test I got an error for the default experiment test:
Start 25: ctest_fmi2_import_default_experiment_test
25/35 Test #25: ctest_fmi2_import_default_experiment_test ............***Failed 0.10 sec
<...>
The following tests FAILED:
25 - ctest_fmi2_import_default_experiment_test (Failed)
Errors while running CTest
make: *** [test] Error 8
The library itself was compiled well and is located in the install directory.
Should I worry about this test failure?
Best wishes,
I.E.
The text was updated successfully, but these errors were encountered: