OMCompiler: Relocatable compilation tools

[jschueller]

Related Issues

The location of compilation tools (cmake & gcc) for fmu export might not be the same when OM is compiled on a different machine than the one on which it will be used (eg conda packages built from conda-forge automatic builders),
and in that case the export can fail (the _build_env directory only existed on the build machine):

Error: Error building simulator. Build log: cmd: cd 'deviation.fmutmp/sources/' && mkdir build_cmake_dynamic && cd build_cmake_dynamic && \"/home/conda/feedstock_root/build_artifacts/omcompiler_1709022273479/_build_env/bin/cmake\" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_COMPILER='/home/runner/miniconda3/envs/test/bin/x86_64-conda-linux-gnu-cc' -DCMAKE_CXX_COMPILER='/home/conda/feedstock_root/build_artifacts/omcompiler_1709022273479/_build_env/bin/x86_64-conda-linux-gnu-c++' .. && \"/home/conda/feedstock_root/build_artifacts/omcompiler_1709022273479/_build_env/bin/cmake\" --build . --parallel  --target install && cd .. && rm -rf build_cmake_dynamic
/bin/sh: 1: /home/conda/feedstock_root/build_artifacts/omcompiler_1709022273479/_build_env/bin/cmake: not found

Purpose

Allow for usable fmu export on conda-forge

Approach

I patched OM to drop absolute paths (and rely on PATH)
xref https://github.com/conda-forge/omcompiler-feedstock/blob/main/recipe/meta.yaml

[mahge]

#9563 for reference.

I think it should have been as you have done it now. I am not sure what exactly was the issue that made us change it to be hard coded. In any case, considering OMDev's cmake has been updated to a good enough version since then, we should be fine using the CMake found on path and falling back to it if all fails.

[jschueller]

could this be included in 1.22.3 ?

[AnHeuermann]

I wouldn't back port it to 1.22. Only really bad bugs should be ported to the maintenance branch.
The next release of OpenModelica should be published soonish and you can use the nightly if your need this fix right now.

[jschueller]

fair enough, I'll wait 1.23