Run GEOS from install dir in experiment - #890
Draft
mathomp4 wants to merge 5 commits into
Draft
Conversation
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 is part of a suite of PRs to try and change how we handle
GEOSgcm.xin GEOS. The issue is that more and more of GEOS subcomponents are becoming shared object libraries instead of static.Overall Problem
That means the old trick of "copy someone else's
GEOSgcm.xto my experiment" might not work. Why? Well, in GEOSgcm v11.10+, the Moist GridComp (for example) is now a shared object library and so just copyingGEOSgcm.xisn't enough to actually use that other person's Moist GC code.What we change here
What we do now is copy into experiments a new
install/binandinstall/libdirectory. The former hasGEOSgcm.xas well asbinarytile.xandrs_numtiles.x(as they are the main executables in the run scripts) and then all the.sointoinstall/lib. We then update the scripts to use those executables.Since CMake encodes in the executable's
RUNPATH,$ORIGIN/../libthen if you run:it will look for libraries it needs in
$ORIGIN/../liband that is just thelib/dir at the same level asEXPDIR/install/bin.