Previously we would run the install rules each time rapids_cpm_cccl was called, since we checked for CCCL_SOURCE_DIR and that could have been defined by an earlier invocation at the same scope.
This causes issue when the first invocation of rapids_cpm_cccl used a custom install location.
CMake's install rules would use the first location, but CCCL install files would contain the second location since they got re-configured on each execution.
vyasr
commented
10 months ago
Description
Previously we would run the install rules each time rapids_cpm_cccl was called, since we checked for
CCCL_SOURCE_DIRand that could have been defined by an earlier invocation at the same scope.This causes issue when the first invocation of
rapids_cpm_ccclused a custom install location. CMake's install rules would use the first location, but CCCL install files would contain the second location since they got re-configured on each execution.Checklist