cmake: Properly handle CUDA toolkit dependency #96
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
…) FindCUDAToolkit module
Codecov Report
@@ Coverage Diff @@
## master #96 +/- ##
=======================================
Coverage 97.83% 97.83%
=======================================
Files 27 27
Lines 1613 1613
=======================================
Hits 1578 1578
Misses 35 35Continue to review full report at Codecov.
|
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.
While the handling of the thrust and OpenMP dependencies has been fixed (see #94 #92), an equivalnt logic for the CUDA toolkit is still missing. Add an oversimplified
FindCUDAToolkit.cmakemodule, which detects the cudart library, to properly specify the CUDA dependency (in non-CUDA files). This also significantly simplifies the GPU Compute Capability detection code.