Closed ClemensLinnhoff closed 1 year ago
There is a problem with dynamically linking the esminilib to the esmini FMU. This is why the pipeline currently fails. I addresses this problem in this issue in the esmini repo.
Separately caching the esminiLib at the correct path work. Now the co-simulation with esmini is running the pipeline!
This is only a temporary solution and in the long run the library should be statically linked against the esmini FMU. However, since it works for now, I suggest we merge this solution already and fix the linking issue when it is fixed in the esmini repo. I created a separate issue #34, to keep it in mind.
Is OpenMCX spinning up a single process per FMU? https://github.com/eclipse/openmcx/issues/10
How is the shared memory in this case defined to exchange data from FMU1 to FMU2?
There is a problem with dynamically linking the esminilib to the esmini FMU. This is why the pipeline currently fails. I addresses this problem in this issue in the esmini repo.
This is now fixed in esmini.
Reference to a related issue in the repository Fixes #32
Add a description
Take this checklist as orientation for yourself, if this PR is ready for Maintainer Review