Integrating mfem in existing CMake project #5009
-
|
Hello, I apologize if this question has already been answered. I am trying to port some of the solvers in my code to mfem but am running into issues using FetchContent_Declare and FetchContent_MakeAvailable regarding the use of relative paths in the mfem CMake config. My CMake config looks like the following. CMake outputs the following logs. Where I replaced my build directory with <build_dir>. To me, this reads as the mfem CMake configuration is prefixing the absolute paths of the metis and hypre installs which is leading to configuration errors. Is there a known fix for this? Or is there a more desirable way to integrate mfem into existing CMake projects? Mfem is not already installed on machines I am hoping to run on hence my use of FetchContent_Declare and FetchContent_MakeAvailable. Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
I usually simply work with the following minimal file and build mfem manually in a separate folder. |
Beta Was this translation helpful? Give feedback.
I usually simply work with the following minimal file
and build mfem manually in a separate folder.