modelica
Provide CMake configuration as proof of concept for future standardization
This issue is opened on behalf of the MAP-Lang design meeting taking place this week.
On the topic of improving the handling of external code in Modelica, the language group wants to go in the direction of standardizing on the use of CMake for building external code:
- https://github.com/modelica/ModelicaSpecification/issues/1668#issuecomment-1468428017
We believe that instead of starting with standardizing this in the Modelica specification, it would be better to first work out a good CMake configuration for the MSL, that tool vendors can try out and contribute to if they want to. When the MAP-Lib and interested tool vendors are satisfied with the setup, we can then proceed with standardization in the language group.
The idea isn't new, but it seems it hasn't been discussed for the 10 last years:
- https://github.com/modelica/ModelicaStandardLibrary/issues/1155
- https://github.com/modelica/ModelicaStandardLibrary/issues/1067#issuecomment-272630259
Maybe someone could shed some light on what CMake file that this comment from 2016 refers to?
- https://github.com/modelica/ModelicaStandardLibrary/issues/1856#issuecomment-272677300
@maltelenz, would you be interested in providing something based on what we do at Wolfram?
FYI: Though M_DD is a header-only library there is a CMake configuration available in https://github.com/modelica-3rdparty/Modelica_DeviceDrivers/blob/master/Modelica_DeviceDrivers/Resources/CMakeLists.txt contributed by @bernhard-thiele .
Maybe someone could shed some light on what CMake file that this comment from 2016 refers to?
I guess it should read Makefile (instead of CMake-file).
Maybe someone could shed some light on what CMake file that this comment from 2016 refers to?
I guess it should read Makefile (instead of CMake-file).
Thanks. Let's consider this item resolved.