v11: Update to ESMA_cmake v3.56.0, FV3 GC v2.13.0, ESMA_env v4.29.2 #863
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 updates ESMA_cmake to use the
LOCATION
strategy for finding Python. This is needed as NAS (at least) has a very recent, but empty (no f2py) Python stack in the default path. UsingLOCATION
should limit it to the Python we want (e.g., via GEOSpyD module)We also update to ESMA_env v4.29.2. This change updates g5_modules to use an MPT 2.30 Baselibs at NAS. This is due to NAS updating the
mpi-hpe/mpt
module tompi-hpe/mpt.2.30
. While this does not break GEOS, CMake throws more errors due to differences in MPT that built Baselibs vs MPT that would build GEOS.It also moves up to Baselibs 7.27.0 which has the latest libraries.
We also update to FV3 GC v2.13.0. This release adds a dependency to
fms_r4
. We need this because of the weird way we build FV3 as r4 but link to the r8 version of FMS. In that case, we still need to point to the include files from r4 FMS.But, CMake in that case has no idea that to build, say, Moist, that we need to build
fms_r4
before building this.