Add premake5-cuda (community) module to doc #2183
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
CUDA support has been queried multiple times (#2168, #1898 etc.). I have been maintaining this module for quite some time, so listing it here would let people use CUDA with Visual Studio (and on Linux). Signed-off-by: thecomputekid <[email protected]>
Open
KyrietS
approved these changes
Feb 12, 2024
nickclark2016
approved these changes
Feb 12, 2024
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.
What does this PR do?
CUDA support has been queried multiple times (#2168, #1898 etc.). I have been maintaining this module for quite some time, so listing it here would let people use CUDA with Visual Studio (and on Linux). This PR was motivated by this comment.
How does this PR change Premake's behavior?
This is a doc-only community change, outside of premake's codebase, therefore it is the maintainer's choice on whether to close those CUDA-related issues.