[CMake] Why does CMake 3.9.0 open VS2017 when targeting 2013 after installing 2017... sigh.

J. Caleb Wherry calebwherry at gmail.com
Mon Oct 1 21:18:29 EDT 2018


The Visual C++ team sheds a little more light on this:

https://blogs.msdn.microsoft.com/vcblog/2018/10/01/cuda-10-is-now-available-with-support-for-the-latest-visual-studio-2017-versions/

Glad they listened to the community and worked with NVIDIA to make this
work.

We’ve been holding off migrating from VS2015 to VS2017 because of the pain
points with CUDA so I’m glad it’s (hopefully) behind us.

-Caleb

On Thu, Sep 20, 2018 at 8:46 AM Robert Maynard <robert.maynard at kitware.com>
wrote:

> In news CUDA 10 release notes include the statement:
>
> - Starting with CUDA 10.0, nvcc supports all versions of Visual Studio
> 2017 (past and upcoming updates)
>
> So the problems of matching VS versions and CUDA versions should be behind
> us.
>
> On Sat, Aug 18, 2018 at 11:56 AM Brian Davis <bitminer at gmail.com> wrote:
>
>>
>> With CUDA 8.0 and 9.0 installed and Visual Stuido 2013 (and god only
>> knows what versions of 2017 updated up grades with whatever tools versions)
>>
>>
>> CMake -> Visual Studio 12 2013 Win64 -> Optional toolset to use
>> (arguments to -T -> cuda=8.0
>>
>> The CXX compiler identification is MSVC 18.0.31101.0
>>
>> The CUDA compiler identification is NVIDIA 8.0.60
>>
>> Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual
>> Studio 12.0/VC/bin/x86_amd64/cl.exe
>>
>> Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual
>> Studio 12.0/VC/bin/x86_amd64/cl.exe -- works
>>
>> Detecting CXX compiler ABI info
>>
>> Detecting CXX compiler ABI info - done
>>
>> Detecting CXX compile features
>>
>> Detecting CXX compile features - done
>>
>> Check for working CUDA compiler: C:/Program Files/NVIDIA GPU Computing
>> Toolkit/CUDA/v8.0/bin/nvcc.exe
>>
>> Check for working CUDA compiler: C:/Program Files/NVIDIA GPU Computing
>> Toolkit/CUDA/v8.0/bin/nvcc.exe -- works
>>
>> Detecting CUDA compiler ABI info
>>
>> Detecting CUDA compiler ABI info - done
>>
>> Found OpenGL: opengl32
>>
>>
>> So, ok finds CUDA 8.0 nvcc
>>
>>
>> CMake -> Visual Studio 15 2017 Win64 -> Optional toolset to use
>> (arguments to -T -> cuda=8.0
>>
>> Selecting Windows SDK version 10.0.17134.0 to target Windows 10.0.16299.
>>
>> The CXX compiler identification is MSVC 19.15.26726.0
>>
>> The CUDA compiler identification is unknown
>>
>> Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual
>> Studio/2017/Community/VC/Tools/MSVC/14.15.26726/bin/Hostx86/x64/cl.exe
>>
>> Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual
>> Studio/2017/Community/VC/Tools/MSVC/14.15.26726/bin/Hostx86/x64/cl.exe --
>> works
>>
>> Detecting CXX compiler ABI info
>>
>> Detecting CXX compiler ABI info - done
>>
>> Detecting CXX compile features
>>
>> Detecting CXX compile features - done
>>
>> CMake Error at CMakeLists.txt:14 (PROJECT):
>> No CMAKE_CUDA_COMPILER could be found.
>>
>>
>> Though I am pretty sure it's there
>>
>>
>> Directory of c:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v9.0\bin
>>
>> 08/15/2018 06:47 PM <DIR> .
>> 08/15/2018 06:47 PM <DIR> ..
>> 09/02/2017 08:45 AM 163,840 bin2c.exe
>> 08/15/2018 06:46 PM <DIR> crt
>> 07/10/2018 04:50 PM 60,549,120 cublas64_90.dll
>> 09/02/2017 08:45 AM 347,136 cuda-memcheck.exe
>> 09/02/2017 08:45 AM 3,930,112 cudafe++.exe
>> 09/02/2017 08:45 AM 4,226,048 cudafe.exe
>> 09/02/2017 08:46 AM 299,520 cudart32_90.dll
>> 09/02/2017 08:46 AM 373,760 cudart64_90.dll
>> 08/15/2018 10:07 AM 288,159,744 cudnn64_7.dll
>> 09/02/2017 08:46 AM 131,197,952 cufft64_90.dll
>> 09/02/2017 08:46 AM 199,680 cufftw64_90.dll
>> 09/02/2017 08:46 AM 3,575,808 cuinj32_90.dll
>> 09/02/2017 08:46 AM 4,495,360 cuinj64_90.dll
>> 09/02/2017 08:45 AM 1,411,072 cuobjdump.exe
>> 09/02/2017 08:46 AM 48,057,344 curand64_90.dll
>> 09/02/2017 08:46 AM 75,222,016 cusolver64_90.dll
>> 09/02/2017 08:46 AM 54,782,464 cusparse64_90.dll
>> 09/02/2017 08:45 AM 246,784 fatbinary.exe
>> 09/02/2017 08:46 AM 1,274,880 gpu-library-advisor.exe
>> 09/02/2017 08:46 AM 205,824 nppc64_90.dll
>> 09/02/2017 08:46 AM 9,744,384 nppial64_90.dll
>> 09/02/2017 08:46 AM 3,953,664 nppicc64_90.dll
>> 09/02/2017 08:46 AM 1,035,264 nppicom64_90.dll
>> 09/02/2017 08:46 AM 7,291,392 nppidei64_90.dll
>> 09/02/2017 08:46 AM 55,641,088 nppif64_90.dll
>> 09/02/2017 08:46 AM 26,491,904 nppig64_90.dll
>> 09/02/2017 08:46 AM 4,767,232 nppim64_90.dll
>> 09/02/2017 08:46 AM 14,943,232 nppist64_90.dll
>> 09/02/2017 08:46 AM 179,200 nppisu64_90.dll
>> 09/02/2017 08:46 AM 2,629,120 nppitc64_90.dll
>> 09/02/2017 08:46 AM 9,024,512 npps64_90.dll
>> 07/10/2018 04:49 PM 241,664 nvblas64_90.dll
>> *09/02/2017 08:45 AM 325,632 nvcc.exe*
>> 09/02/2017 08:45 AM 328 nvcc.profile
>> 09/02/2017 08:45 AM 16,261,120 nvdisasm.exe
>> 09/02/2017 08:46 AM 15,747,584 nvgraph64_90.dll
>> 09/02/2017 08:45 AM 7,202,304 nvlink.exe
>> 09/02/2017 08:45 AM 4,005,376 nvprof.exe
>> 09/02/2017 08:45 AM 181,248 nvprune.exe
>> 09/02/2017 08:46 AM 3,182,592 nvrtc-builtins64_90.dll
>> 09/02/2017 08:46 AM 17,302,016 nvrtc64_90.dll
>> 09/02/2017 08:46 AM 53 nvvp.bat
>> 05/16/2018 04:16 PM 7,082,496 ptxas.exe
>> 42 File(s) 885,951,869 bytes
>> 3 Dir(s) 675,381,178,368 bytes free
>>
>>
>> Dare I ask/look to see how CMake finds nvcc these days?
>>
>>
>> Dare I ask the question: Is CMake compatible/does it work with Visual
>> Studio and CUDA anymore? Have we entered the days where CMake is always x^N
>> versions behind VS and CUDA?
>>
>>
>> Is there a test case in CMake I can run to check to see if it works with
>> my VS Version (2017 15.1, 15.2, 15.3, 15.4, 15.5 (from MS web link above)
>> +++ granted I am now running after update 15.8.1) and CUDA 8.0, 9.0, 9,1.
>>
>>
>> Is there a CMake compatibility chart some where I can plug in my versions
>> on a x/y table to see if it sunk my battle ship?
>>
>>
>> --
>>
>> 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:
>> https://cmake.org/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:
> https://cmake.org/mailman/listinfo/cmake
>
-- 
Sent from my iPhone 4s
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://cmake.org/pipermail/cmake/attachments/20181001/03bcfdae/attachment-0001.html>


More information about the CMake mailing list