So you are going to have two issues. 1. The FindCUDA module has not been updated to handle VS2017. The issue is that the VCInstallDir variable now returns a different relative path to the compiler than it previously did. If you can determine the new logic a patch fixing this behavior be great.
2. It doesn't look like CUDA 8.0 supports VS2017 ( http://docs.nvidia.com/cuda/cuda-installation-guide-microsoft-windows/index.html#system-requirements ). 3. You could also look at using the new CMake 3.9 cuda support ( https://devblogs.nvidia.com/parallelforall/building-cuda-applications-cmake/ ). On Thu, Aug 10, 2017 at 5:49 AM, Andrea Borsic <abor...@gmail.com> wrote: > Hi All, > > I am working on this platform: > > Windows 10 64bit > Visual Studio 2015 Community Edition > Visual Studio 2017 Community Edition > CUDA 8.0 > CMake 3.9 > > I am in the middle of switching from VS2015 to VS2017, but CUDA projects > fail to properly compile under VS2017 as the compiler/linker fail to find > tools on the path setup by CMake. I believe this is bug/incompatibly of the > CMake FindCUDA module with VS2017. > > To reproduce the problem I am attaching a tiny project > > main.cu is a minimal CUDA example from the web > CMakeLists.txt is a CMake file that leads to a successful build under VS2015 > and unsuccessful under VS2017 > Output VS2015 is the output from building the project under VS2015 (all > targets built OK) > Output VS2017 is the output from building the project under VS2015 (1 target > OK one target fails) > > I have noticed also that oddly under VS2017 an "x64" and "main.dir" > directories are created outside the build dir, and at the level of the > source directory. > > I thought of reporting this to the list, and any help is welcome, > > Thank you and Best Regards, > > Andrea > > > -- > > Powered by www.kitware.com > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Kitware offers various services to support the CMake community. For more > information on each offering, please visit: > > CMake Support: http://cmake.org/cmake/help/support.html > CMake Consulting: http://cmake.org/cmake/help/consulting.html > CMake Training Courses: http://cmake.org/cmake/help/training.html > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/cmake -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake