consistent use of _USE_ and _HAS_ cmake variables #618
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
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.
Variables in cmake called
*_USE_*are always user-defined, and are not modified by any cmake script (except for GRAPHBLAS_USE_CUDA which is not yet available in production).Variables in cmake called
*_HAS_*are set by cmake, not by the user who builds SuiteSparse. For example, if OpenMP is requested, the_USE_isON/OFF. Then if it is found and OK to use (v2.0 for most packages, v4.5 for ParU), then the corresponding_HAS_variable is setON/OFF.