-
Notifications
You must be signed in to change notification settings - Fork 24
Check for CUDA headers rather than compiler #28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
sethrj
wants to merge
8
commits into
root-project:master
Choose a base branch
from
sethrj:cuda-header-config
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
cece62b
Self-report installation location
sethrj cd1b41c
Look for CUDA toolkit instead of compiler since only headers are needed
sethrj 066b677
Update cuda compatibility
sethrj 20f672e
Add test
sethrj d54d4ec
Enable language
sethrj 534eb09
Update cmake compatibility
sethrj d3b4bd5
Revert "Enable language"
sethrj 7dbc9d2
Empty commit to retry CI
sethrj File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you please explain the motivation for this change? The current way of doing things follows advice from CMake policy CMP0146, which suggests projects should use CMake's first class support for cuda via
check_language(CUDA)/enable_language(CUDA). The addition of-DVECCORE_ENABLE_CUDAdoes require that the CUDA language be enabled if you are compiling CUDA code, because that will enable host/device macros, etc. If you want to handle that yourself, you can alwaysfind_package(VecCore)without specifying theCUDAcomponent, thenadd_definitions(VECCORE_ENABLE_CUDA)yourself, without having to change this logic.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the record, this was last modified in this commit 743566f.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The article you link is about CUDA compilation, and
CUDAToolkitis about locating the libraries. Since VecCore doesn't build any CUDA files at all, it doesn't need to enable the full language: linking againstCUDA::cudart(or includingCUDAToolkit_INCLUDE_DIRS) letscuda_runtime.hand the associated macros to be found by C++ compilers.