Replies: 3 comments
-
@ischeider I fully support this. I moved these parameters to their current place a few years ago since they were duplicated in all the user configurations but that is not how we should do it. Our CMake setup is a lot saner these days, so I am sure we can find a better way here. |
Beta Was this translation helpful? Give feedback.
-
For me it would be sufficient to replace the The other option I see is to have an
in the CMakeLists.txt. What do you prefer? |
Beta Was this translation helpful? Give feedback.
-
AFAICS, the PR #727 changes the behavior, so the discussion can be closed. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Some machines, particularly HPC systems, often have a specific configuration, which makes it necessary that mpirun gets parameters different from the standard, which are as of now hardcoded in
CMakeLists.txt
:At least @ppraegla and me need some other and/or added parameters. Anybody else, who also would like to have more flexibility in the generation of the
CTestTestfile.cmake
?For example, if we introduce an environment variable, which can be set by users (or even system administrators) and maybe has some default, e.g., the variables defined above, we avoid breaking the compliance by hard-coding particular parameters in the repo.
Beta Was this translation helpful? Give feedback.
All reactions