v11: Add Build Info, Update ESMA_env, ESMA_cmake, FV3 GC#930
Merged
Conversation
This was referenced May 12, 2025
This was referenced May 13, 2025
sdrabenh
approved these changes
Jun 4, 2025
This file contains hidden or 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
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.
This PR is from a conversation with myself and Nicko Acks of NCCS. Namely, it would be nice to have a file that determines build information of a GEOS build.
This PR requires some updates to ESMA_env and ESMA_cmake.
This also updates ESMA_env to use Baselibs 7.33.0 which has updates really needed for MAPL3 work.
We also update to GMAO_Shared v2.1.1 with another fix for f2py
We also update to FV3 GC v2.14.1 which adds a missing export.
This is some example output: