Using the ThirdPartyLibraries with the pangea3-gcc8.4.1-openmpi-4.1.2.cmake host-config file and the -DENABLE_CUDA=OFF option compiles HYPRE with CUDA flags and the other TPLs without CUDA flags. This results in a set of software that can't be used to build Geos.
This PR proposes to ensure that the entire suite of TPLs is built with compatible flags (so the build of Geos will not fail):
if the ENABLE_CUDA variable is explicitely setted to OFF by the user and Hypre is asked to be built with CUDA, a warning is raised saying that Hypre will ignore the CUDA config.
Even if useless with the previous modification, I find it useful to provide to the user host-config files where dependencies between options are explicitely shown so I have modified the P3 host-config file in order to set Hypre device to CUDA only when ENABLE_CUDA is on.
Using the ThirdPartyLibraries with the
pangea3-gcc8.4.1-openmpi-4.1.2.cmakehost-config file and the-DENABLE_CUDA=OFFoption compiles HYPRE with CUDA flags and the other TPLs without CUDA flags. This results in a set of software that can't be used to build Geos.This PR proposes to ensure that the entire suite of TPLs is built with compatible flags (so the build of Geos will not fail):
ENABLE_CUDAvariable is explicitely setted toOFFby the user andHypreis asked to be built withCUDA, a warning is raised saying that Hypre will ignore theCUDAconfig.Hypre devicetoCUDAonly whenENABLE_CUDAison.It is linked to: