We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Something else
CCCL
In cccl-config.cmake, the check for CCCL_ENABLE_UNSTABLE always returns false.
CCCL_ENABLE_UNSTABLE
Instead, the check should be
if(DEFINED ENV{CCCL_ENABLE_UNSTABLE} AND "$ENV{CCCL_ENABLE_UNSTABLE}") # .... endif()
Set CCCL_ENABLE_UNSTABLE=ON or any truth value and try to import CCCL::cudax
CCCL_ENABLE_UNSTABLE=ON
CCCL::cudax
Doing the above should include the cudax target.
cudax
N/A
The text was updated successfully, but these errors were encountered:
@alliepiper any chance you already took care of this as part of the cleanup you're doing?
Sorry, something went wrong.
Nope, but I'll add it to the list.
This is working as intended. That is not an environment variable, but rather a cmake variable that should be defined before find_package(CCCL).
find_package(CCCL)
set(CCCL_ENABLE_UNSTABLE ON) find_package(CCCL)
This is working as intended. That is not an environment variable, but rather a cmake variable that should be defined before find_package(CCCL). set(CCCL_ENABLE_UNSTABLE ON) find_package(CCCL)
Yes, verified that this works! I misunderstood the README, thinking it was an env variable.
alliepiper
No branches or pull requests
Is this a duplicate?
Type of Bug
Something else
Component
CCCL
Describe the bug
In cccl-config.cmake, the check for
CCCL_ENABLE_UNSTABLE
always returns false.Instead, the check should be
How to Reproduce
Set
CCCL_ENABLE_UNSTABLE=ON
or any truth value and try to importCCCL::cudax
Expected behavior
Doing the above should include the
cudax
target.Reproduction link
Operating System
N/A
nvidia-smi output
N/A
NVCC version
N/A
The text was updated successfully, but these errors were encountered: