Add code to find CGNS tools #187
Merged
Conversation
This file contains 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
Add code that will find CGNS tools -- cgnscheck, cgnsdiff, cgnslist, cgnscompress, cgnsconvert, cgnsnames, cgnsupdate.
For each of these that is found, the symbol CGNS_{command_uppercase}_BINARY will be defined. These are useful for tests of applications/routines that access CGNS files -- the testing code can check whether a specific command exists and act accordingly.
The NetCDF and HDF5 Find routines contain similar code and naming conventions.
|
Any idea when this will be merged? |
|
Sorry, just saw this (I don't seem to be getting many of these GitHub email notifications). I will move this back up higher on my personal todo list. |
|
Is this still on your backlog for merging? |
|
Sorry, I should have merged this a long time ago. I just don't have any way to test this. |
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.
Add code that will find CGNS tools -- cgnscheck, cgnsdiff, cgnslist, cgnscompress, cgnsconvert, cgnsnames, cgnsupdate.
For each of these that is found, the symbol CGNS_{command_uppercase}_BINARY will be defined. These are useful for tests of applications/routines that access CGNS files -- the testing code can check whether a specific command exists and act accordingly.
The NetCDF and HDF5 Find routines contain similar code and naming conventions.