-
Notifications
You must be signed in to change notification settings - Fork 99
Allow lfric_atm to compile for oasis coupled models #486
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
Open
Paul Earnshaw (pdearnshaw)
wants to merge
6
commits into
MetOffice:main
Choose a base branch
from
pdearnshaw:92_coupled_compilation_fix
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+20
−1
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
0ec2417
Copied in changes from head of final subversion branch.
pdearnshaw d53ad32
Added missing variable for coupled model configurations.
pdearnshaw 06e575d
Merging in stable vn3.1 and resolving conflicts associated with lfric…
pdearnshaw ffd66a8
#92. Fixed some changes from attempt to merge in stable, which actual…
pdearnshaw 919fa0a
#92. Added name to contributors file.
pdearnshaw d189844
Merge tag 'vn3.1.1' into 92_coupled_compilation_fix
pdearnshaw File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Normally we would just test for the existence of the macro. What is the reason for requiring it to have a particular value?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
COUPLEDhere is not a macro, it is an environment variable. What we want in this test is to make sure firstly that it has been set, and then that it has been set toTrue. The idea being that if it is not set, or set toFalsethen the coupled model infrastructure is not applied.As I understand it the
ifdefstatement can test for environment variables or keyword-like arguments in themakecommand, it cannot act onPRE_PROCESS_MACROentries. So the choice in how to identify if we wanted to compile as a coupled model was to use an optional environment variable.Happy to consider other ways of doing this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
PRE_PROCESS_MACROSare converted into a set of-D<key>=<value>arguments to the compiler. So they will appear to the preprocessor as macros. In which case you can just test on their presence. Unless you think there will be cases where people are setting that value toFalse.There's no correctness reason not to do it the way you have, it just runs the risk of people getting unexpected behaviour if they say
COUPLED=YES.I don't mind which you do so feel free to resolve this conversation when you have made a decision.