Incomplete CMake config

[stgeke]

Important options are missing

• HIP
• Umpire
• enable-device-malloc-async
• enable-gpu-aware-mpi
• ...

[lahwaacz]

IMHO there should be only one build system supported, otherwise they will always diverge at some point. Is there a reason to keep the configure script and Makefiles instead of moving towards CMake?

[rfalgout]

Hi @stgeke and @lahwaacz . We are working on the CMake support for this. Regarding having two build systems, I agree that it is difficult to support two, and it would be better from a maintenance point-of-view to only have one. However, for the moment we will need to continue this way because we have important customers who use the autoconf system (our original build system) and we want to make sure they have migrated over to CMake before we consider dropping autoconf. Also, our main developers are more familiar with autoconf and it will take some time for us to fully embrace CMake as our primary build tool, but that is the plan.

However, please tell us when you find inconsistencies or problems with either system. It is very helpful. Thanks!

[streeve]

We are hoping to use HIP through CMake, but are also looking into selectively supporting autotools builds (see ECP-copa/Cabana#658). Any updates here or thoughts on whether we could plausibly help with adding HIP CMake support?

[stgeke]

Any updates on this? In particular HIP + CMake support.