lib/OMSimulator directory contains duplicated files

[adeas31]

Description

After installing the latest OpenModelica nightly build I noticed that there are around 700 MB of files duplicated inside lib/OMSimulator folder.

Steps to reproduce the behavior

Install OpenModelica on Windows and take a look at lib/OMSimulator folder. The same files are also present in the bin folder as well.

Expected behavior

lib/OMSimulator should only contain the OMSimulator binaries.

Screenshots

Version and OS

• Version: [Doesn't matter]
• OS: [Win10, 64bit]

[lochel]

Unfortunately, we cannot just delete the duplicated files, because we depend on the path:

@AnHeuermann Do you see a way to solve this issue?

[AnHeuermann]

We could add a bunch of symbolic links. Or change the paths if we compile OMSimulator from OpenModelica super project.

[lochel]

Changing the path when compiling from the super project sounds like the right thing to do 👍

[adeas31]

Unfortunately, we cannot just delete the duplicated files, because we depend on the path:

Expected behavior

lib/OMSimulator should only contain the OMSimulator binaries.

For sure keep the binaries needed by OMSimulator but why there are folders for Qt plugins? I think the problem is you just make a copy of bin folder https://github.com/OpenModelica/OMSimulator/blob/master/src/OMSimulatorPython/CMakeLists.txt#L29

[lochel]

@adeas31 can this be closed or do we have to improve it further?

[adeas31]

Is better than before but would be nice to get rid of empty directories as well.

[lochel]

I didn't find a good solution to avoid the empty directories. @AnHeuermann do you have a idea for it?

[AnHeuermann]

We can just call rm on them in the Makefile calling the CMake stuff. Not a pretty solution but should work.

[adeas31]

@AnHeuermann solution is not so bad.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.