Currently, when GHEX is configured using CMake and installed, the configured options are hard-coded into the installed GHEX Cmake config file. Since this file is then included by the user in his cmake config, he can only use GHEX in the form it was configured (e.g., with either UCX, or MPI backend).
Since at this point GHEX is header-only, this is not necessary. We could allow the user to change the GHEX configuration in his cmake configuration by, .e.g, exporting the available configuration options in the installed GHEX cmake config, instead of hard-coding them. The user could then choose whatever he wants without having to re-configure and re-install GHEX separately.
Currently, when GHEX is configured using CMake and installed, the configured options are hard-coded into the installed GHEX Cmake config file. Since this file is then included by the user in his cmake config, he can only use GHEX in the form it was configured (e.g., with either UCX, or MPI backend).
Since at this point GHEX is header-only, this is not necessary. We could allow the user to change the GHEX configuration in his cmake configuration by, .e.g, exporting the available configuration options in the installed GHEX cmake config, instead of hard-coding them. The user could then choose whatever he wants without having to re-configure and re-install GHEX separately.