You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
To enforce consumers to use RAPIDS add deprecation notices when a project uses the older magic values.
Describe the solution you'd like
Large CMake deprecation warning that this will be released in the N+1 version of rapids-cmake with documentation on how to fix.
Would use message(AUTHOR_WARNING
The text was updated successfully, but these errors were encountered:
We need to be careful when we run into nested projects that all use rapids-cmake but of different versions ( 22.10 vs 23.02 ).
In those cases we need to preserve backwards compat, so functions like rapids_cuda_set_architectures need to behave in a 22.10 mode.
I believe that we can check the rapids-cmake-version value and switch to old behavior when needed ( with extra notifications about updating to latest rapids-cmake version ).
Is your feature request related to a problem? Please describe.
To enforce consumers to use
RAPIDS
add deprecation notices when a project uses the older magic values.Describe the solution you'd like
Large CMake deprecation warning that this will be released in the N+1 version of rapids-cmake with documentation on how to fix.
Would use
message(AUTHOR_WARNING
The text was updated successfully, but these errors were encountered: