-
Notifications
You must be signed in to change notification settings - Fork 46
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
[FEA] rapids-cmake pinning override allow generation via CMake variable #552
Labels
Comments
robertmaynard
added
feature request
New feature or request
? - Needs Triage
Need team to review and classify
labels
Mar 5, 2024
4 tasks
rapids-bot bot
pushed a commit
that referenced
this issue
May 3, 2024
Extends #595 with support for setting the default and override file used by rapids-cmake via the command line. Fixes #552 #587 Authors: - Robert Maynard (https:/robertmaynard) Approvers: - Vyas Ramasubramani (https:/vyasr) URL: #596
Was incorrectly associated to PR #596. This task still needs implementing |
robertmaynard
added a commit
to robertmaynard/rapids-cmake
that referenced
this issue
May 3, 2024
3 tasks
robertmaynard
added a commit
to robertmaynard/rapids-cmake
that referenced
this issue
May 7, 2024
robertmaynard
added a commit
to robertmaynard/rapids-cmake
that referenced
this issue
May 10, 2024
rapids-bot bot
pushed a commit
that referenced
this issue
May 10, 2024
Fixes #552 Authors: - Robert Maynard (https:/robertmaynard) Approvers: - Kyle Edwards (https:/KyleFromNVIDIA) URL: #600
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Is your feature request related to a problem? Please describe.
We should think about allowing projects that want to use
rapids_cpm_generate_pinned_versions
to do so without having to modify the CMake logic of the project.Describe the solution you'd like
We should support generation via a CMake variable such as
RAPIDS_CMAKE_GENERATE_PINNED_VERSIONS
Describe alternatives you've considered
Thought about env variables, doesn't feel explicit enough.
Additional context
#530 (review)
The text was updated successfully, but these errors were encountered: