Replace FindCUDA with FindCUDAToolkit (fix #2833) #3090
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
….txt in test_for_cudnn. Now working on Windows 10 with default install paths.
latest from upstream.
…, do we still need this?
…, do we still need 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.
Attempting to fix #2833 the FindCUDA issue (Policy CMP0146 is not set: The FindCUDA module is removed.)
Working from #3087 and with some help from Tobias. I have this working on Fedora Linux and Windows 10.
I've more recently found #3004 which suggests (referencing #2912) that this may not be possible due to findpkg issues. I've not looked at that but I have been able to update test_for_cuda and test_for_cudnn. I have compiled and run the test as suggested in #3004 and it seems to compile and run.