[BUG]: ThrustInstallRules.cmake doesn't support when CMAKE_INSTALL_LIBDIR is an absolute value
#1390
Closed
1 task done
Labels
bug
Something isn't working right.
Comments
2 tasks
robertmaynard
added a commit
to robertmaynard/cccl
that referenced
this issue
Feb 16, 2024
2 tasks
robertmaynard
added a commit
to robertmaynard/cccl
that referenced
this issue
Feb 20, 2024
alliepiper
pushed a commit
that referenced
this issue
Feb 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this a duplicate?
Type of Bug
Something else
Component
Thrust
Describe the bug
When
CMAKE_INSTALL_LIBDIRis an absolute value the compuations thatThrustInstallRules.cmakedoes to figure out the relative location of the includes fails.How to Reproduce
Pass
-DCMAKE_INSTALL_LIBDIR=${CMAKE_INSTALL_PREFIX}/libon the command lineExpected behavior
When
CMAKE_INSTALL_PREFIXis a parent directory ofCMAKE_INSTALL_LIBDIRit should be possible to compute the correct relative association.It is impossible to always support absolute
CMAKE_INSTALL_LIBDIRvalues, since theCMAKE_INSTALL_PREFIXcan be rewritten at install time when usingcmake --install <dir> --prefix <path>or the entire install tree can be relocated ( e.g. a package manager ).Reproduction link
No response
Operating System
No response
nvidia-smi output
No response
NVCC version
No response
The text was updated successfully, but these errors were encountered: