kokkos: remove restrictions for ~wrapper - #5775
Conversation
Kokkos has had an automatic launch_compiler since 3.3 that will automatically redirect to either host or NVCC. The nvcc_wrapper replacement comes from a time where we needed to explicitly set the CXX compiler to the wrapper. This launch_compiler behavior is the recommended default, so don't artifically force +wrapper in the +cuda case, when it's not actually needed.
I am not against this statement but then maybe we should stop using |
|
@tpadioleau yes, but updating those packages is one or more separate PRs. 6 of those are "mine" to update. |
Cool then we almost have them all, fyi i have ddc, koliop, gmgpolar and kokkos-fft. We should also update the template we provide in Kokkos documentation. |
|
@rbberger Also, I am getting this kind of error https://github.com/tpadioleau/dev-spack/actions/runs/30202966761/job/89796025706 when using a build cache. I have no idea what is happening, I get it with other packages that use |
|
@tpadioleau yeah, I've seen this. I think that logic is just outdated and should be removed. I think we have to return |
|
@tpadioleau I've just tried this with |
Kokkos has had an automatic launch_compiler since 3.3 that will automatically redirect to either host or NVCC. The nvcc_wrapper replacement comes from a time where we needed to explicitly set the CXX compiler to the wrapper. This launch_compiler behavior is the recommended default, so don't artifically force +wrapper in the +cuda case, when it's not actually needed.