You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A grand hope for GEOSgcm (and for @danholdaway in particular) is one day we can do:
spack install geosgcm
and we get a build of GEOSgcm.
I'm currently trying to figure out how to get spack-stack to do that (see JCSDA/spack#174) and I've identified four paths we must look at when building GEOSgcm with Spack:
Build with internal MAPL and internal FMS
Build with internal MAPL and spack FMS
Build with spack MAPL and internal FMS
Build with spack MAPL and spack FMS
I think the FMS bits are fairly simple. I've build GEOS with FMS in Baselibs (see #368), but building GEOS with MAPL as an external library will require some...thought.
I'll probably need to think on it with @tclune at least at first. It must be doable as our UFS colleagues do find_package(MAPL REQUIRED), but do they have a FindMAPL.cmake file somewhere?
The text was updated successfully, but these errors were encountered:
A grand hope for GEOSgcm (and for @danholdaway in particular) is one day we can do:
and we get a build of GEOSgcm.
I'm currently trying to figure out how to get spack-stack to do that (see JCSDA/spack#174) and I've identified four paths we must look at when building GEOSgcm with Spack:
I think the FMS bits are fairly simple. I've build GEOS with FMS in Baselibs (see #368), but building GEOS with MAPL as an external library will require some...thought.
I'll probably need to think on it with @tclune at least at first. It must be doable as our UFS colleagues do
find_package(MAPL REQUIRED)
, but do they have aFindMAPL.cmake
file somewhere?The text was updated successfully, but these errors were encountered: