Amendments to support upcoming DUNE 2.10 release #4202
+3
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DUNE 2,10 moves a step closer to being used by just using
find_package(dune-module)
with targets. It is not completely there as upstream still sets up the targets indune_finalize_project
.Unfortunately, it sets the (unused since 2.7) alias HAVE_UMFPACK in a included header. The compiler warns about this as we explicitly set it 1 instead of HAVE_SUITESPARSE_UMFPACK. Hence we remove it in OPM.
It also set HAVE_DUNE_MODULE to TRUE in the CMake package configuration files. This causes compile errors because we get a
#define HAVE_DUNE_ISTL TRUE
in config.h but TRUE is not defined. Therefore reset the value before we do the out compile check.Still needs to be battle-tested, but works on my system.
Related PRs: