Re-add petsc/ slepc vars to Serac config #1163
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chapman39
changed the title
white238
approved these changes
Jul 2, 2024
tupek2
approved these changes
Jul 2, 2024
zatkins-work
approved these changes
Jul 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In my previous mfem petsc wrapper PR, I removed the petsc/ slepc cmake variables (e.g.
SERAC_USE_PETSC) fromserac-config.cmake.in, which might prevent downstream users of Serac from being able to check whether Serac has been configured with petsc/ slepc support (since mfem installed without petsc/ slepc is still allowed).This is just a small PR that re-adds those cmake variables. I also removed the sundials
find_dependencysection, since sundials is built through MFEM (just like petsc/ slepc), and is therefore not required.