Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Config.h.in: use PETSc/SLEPc macros to determine PETSc/SLEPc version #15770

Merged
merged 1 commit into from Jul 22, 2023

Conversation

stefanozampini
Copy link
Contributor

This allows to use code in the development version

This allows to use code in the development version
@tamiko
Copy link
Member

tamiko commented Jul 20, 2023

/rebuild

Comment on lines +397 to +402
#ifdef DEAL_II_WITH_PETSC
# define DEAL_II_PETSC_VERSION_LT(major,minor,subminor) \
PETSC_VERSION_LT(major,minor,subminor)
# define DEAL_II_PETSC_VERSION_GTE(major,minor,subminor) \
PETSC_VERSION_GE(major,minor,subminor)
#endif
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have these been around for a long time? I believe that they didn't exist when I first wrote the interfaces for PETSc, but that was in 2004/2005. We've long not supported such old versions any more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The only difference is that the PETSc macros also test for PETSC_VERSION_RELEASE which is 1 for a release, 0 for any other commit which is not a tag. For example PETSC_VERSION_LT will always expand to 0 when developing, while PETSC_VERSION_GE will always expand to 1 in the same case.

@bangerth bangerth merged commit b2fcc6e into dealii:master Jul 22, 2023
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants