Thomas Beutlich
Thomas Beutlich
> who takes care of rebuilding the binaries? The library officers do.
> what about PR #4360? This is controversial, see https://github.com/modelica/ModelicaStandardLibrary/pull/4360#issuecomment-2161123419
> @beutlich I'm sorry that I cannot really follow the discussion in #4360, as it is very technical and implementation-related. Could you provide a concrete use case or MWE that...
> do I understand correctly that the built libraries are made available directly in the Modelica\Resources\Library\ resource directory of the GIT repository. The commit history gives the answer: https://github.com/modelica/ModelicaStandardLibrary/commits/master/Modelica/Resources/Library >...
> cherry pick No, #4415 is already back-ported from master to maint/4.1.x via #4417. Hence, that's no more an issue. > Do I miss something else? Yes, I am actually...
> This seems to me a really minor issue. Not sure actually. > If you can find an agreement with @HansOlsson that would be good Well, I was hoping so.
> * rebuild the libraries and place them under Resources on maint/4.1.x There now is #4426.
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).
There now is #4265.