Add preprocessor variable USE_PDAF
#8
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
Every pre-patched change inside ParFlow that relates to PDAF is put under (1) if-condition `USE_PDAF` for CMake-scripts or (2) `#ifdef` preprocessor variable condition for source code.
- to `amps`, `pfsimulator`, where it is used in code
``` CMake Error at pfsimulator/amps/CMakeLists.txt:9 (target_compile_definitions): Cannot specify compile definitions for target "amps" which is not built by this project. ```
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Follow the example of eCLM and add
USE_PDAFin CMake-scripts (if (USE_PDAF)) and source code (#ifdef USE_PDAF) in order to make PDAF-related code immediately visible.Currently results in errors.