Known issue: https://forums.developer.nvidia.com/t/stuck-installing-nsight-on-cuda-12-8-0-571-96-windows/323732/2
(Update: This is a VS bug, DevCom-10841757, expected to be fixed in VS 2022 17.14 Preview 2.)
I encountered this when updating the toolset (from Preview 2) to VS 2022 17.13 Preview 3 in #5247 but didn't understand the cause then.
Unfortunately, my "solution" of installing just 'nvcc_12.4' didn't work, but I didn't realize it. nvcc was no longer being found on the path, causing the test harness to skip GH_000639_nvcc_include_all, and I didn't think to look for this.
I can't figure out how nvcc is normally added to the developer command prompt path (i.e. if there's a particular subpackage that will do it, or only the full installation). As a workaround, I'm going to try to manually add it to the path. I also need to install the CUDA runtime libraries.
This is a tracking issue to remember what's going on here. I'm not sure if this will be fixed on the CUDA side or the VS side. Either way, my workaround should be removed at that time, and if CUDA is the one that's fixed, we should strongly consider increasing our minimum required CUDA version.
Known issue: https://forums.developer.nvidia.com/t/stuck-installing-nsight-on-cuda-12-8-0-571-96-windows/323732/2
(Update: This is a VS bug, DevCom-10841757, expected to be fixed in VS 2022 17.14 Preview 2.)
I encountered this when updating the toolset (from Preview 2) to VS 2022 17.13 Preview 3 in #5247 but didn't understand the cause then.
Unfortunately, my "solution" of installing just 'nvcc_12.4' didn't work, but I didn't realize it.
nvccwas no longer being found on the path, causing the test harness to skipGH_000639_nvcc_include_all, and I didn't think to look for this.I can't figure out how
nvccis normally added to the developer command prompt path (i.e. if there's a particular subpackage that will do it, or only the full installation). As a workaround, I'm going to try to manually add it to the path. I also need to install the CUDA runtime libraries.This is a tracking issue to remember what's going on here. I'm not sure if this will be fixed on the CUDA side or the VS side. Either way, my workaround should be removed at that time, and if CUDA is the one that's fixed, we should strongly consider increasing our minimum required CUDA version.