<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">> Can't that be set by passing the toolset with a -T<br>
</span><br><div id="gmail-:1k5" class="gmail-ajR" tabindex="-1"><div id="gmail-:1k4" class="gmail-bTfW2d"><img class="gmail-ajT" src="https://ssl.gstatic.com/ui/v1/icons/mail/images/cleardot.gif" style="margin-right: 0px;" width="0" height="0"></div></div><span class="gmail-">
</span>That is what I was trying to say with my last sentence. You will need<br>
to use CMake 3.12 to have support for specifying the minor toolset<br>
version though.<br>
<div class="gmail-HOEnZb"><div class="gmail-h5"></div></div></blockquote><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail-HOEnZb"><div class="gmail-h5">>>><br>
>>> The MSVC / CUDA support recently has been very challenging to keep track of. In general CUDA will only support a single patch release of MSVC, and given how MSVC 2017 doesn't easily allow rollbacks and has a pretty aggressive update policy ( compared to older MSVC versions ) causes lots of pain. This in general has been a community wide MSVC+CUDA issue.<br>
>>><br>
>>> CUDA 8 has zero support for VS2017 ( <a href="https://docs.nvidia.com/cuda/archive/8.0/cuda-installation-guide-microsoft-windows/index.html" rel="noreferrer" target="_blank">https://docs.nvidia.com/cuda/<wbr>archive/8.0/cuda-installation-<wbr>guide-microsoft-windows/index.<wbr>html</a> )<br>
>>> CUDA 9.0 and 9.1 only supports VS 2017 15.0 (<a href="https://docs.nvidia.com/cuda/archive/9.0/cuda-installation-guide-microsoft-windows/index.html" rel="noreferrer" target="_blank">https://docs.nvidia.com/cuda/<wbr>archive/9.0/cuda-installation-<wbr>guide-microsoft-windows/index.<wbr>html</a>, <a href="https://docs.nvidia.com/cuda/archive/9.1/cuda-installation-guide-microsoft-windows/index.html" rel="noreferrer" target="_blank">https://docs.nvidia.com/cuda/<wbr>archive/9.1/cuda-installation-<wbr>guide-microsoft-windows/index.<wbr>html</a>)<br>
>>> CUDA 9.2 only supports VS 2017 15.0 and 15.6<br>
>>><br>
>>> When using MSVC 2017 and CUDA you will need to specify an explicit host side compiler with -T version=15.## including the minor version ( <a href="https://cmake.org/cmake/help/v3.12/release/3.12.html#id3" rel="noreferrer" target="_blank">https://cmake.org/cmake/help/<wbr>v3.12/release/3.12.html#id3</a> ).<br>
>><br><br>
> Can't that be set by passing the toolset with a -T ? like -T "v120_xp" or -T "v120"<br>
><br>
> This is an article about side-by-side toolsets <a href="https://blogs.msdn.microsoft.com/vcblog/2017/11/15/side-by-side-minor-version-msvc-toolsets-in-visual-studio-2017/" rel="noreferrer" target="_blank">https://blogs.msdn.microsoft.<wbr>com/vcblog/2017/11/15/side-by-<wbr>side-minor-version-msvc-<wbr>toolsets-in-visual-studio-<wbr>2017/</a> but it looks like it only goes back to 2015...<br>
</div></div></blockquote></div><div class="gmail_quote"><br></div><div class="gmail_quote">Between
<a href="https://blogs.msdn.microsoft.com/vcblog/2017/11/15/side-by-side-minor-version-msvc-toolsets-in-visual-studio-2017/" rel="noreferrer" target="_blank">https://blogs.msdn.microsoft.<wbr>com/vcblog/2017/11/15/side-by-<wbr>side-minor-version-msvc-<wbr>toolsets-in-visual-studio-<wbr>2017/</a> ,
<a href="https://docs.nvidia.com/cuda/archive/8.0/cuda-installation-guide-microsoft-windows/index.html" rel="noreferrer" target="_blank">https://docs.nvidia.com/cuda/<wbr>archive/8.0/cuda-installation-<wbr>guide-microsoft-windows/index.<wbr>html</a>
and
<a href="https://cmake.org/cmake/help/v3.12/release/3.12.html#id3" rel="noreferrer" target="_blank">https://cmake.org/cmake/help/<wbr>v3.12/release/3.12.html#id3</a>
I am wondering if MS, NVIDIA, and CMake can get together and make a super secret decoder ring set (1 CMake, 1 MS, and 1 NVIDIA - imagine the street cred I would have on the internet superhighway if I had that kind of bling) Bluetooth enabled so as to activate the MS's stated "escape hatch" (their words not mine) I am working to install in my bit mine so as I can get quick egress to that when needed. Also MS might consider Bluetooth enabled accessory (shock collar) when decoder ring is put into versions they rather not support as would alleviate the necessity to review the "VS servicing guidelines". Then if when the decoder rings are set to all the correct versions and with their powers combined I could compile an application. Great reads all.<br></div><div class="gmail_quote"><br></div><div class="gmail_quote">So how do I get this to work?</div><div class="gmail_quote"><br></div><div class="gmail_quote">PROJECT(PROJECT_NAME CXX CUDA )<br></div><div class="gmail_quote"><br></div><div class="gmail_quote"><br></div><div class="gmail_quote">and then for 2017 and CUDA 9.0 at the toolset -T line in GUI:<br></div><div class="gmail_quote"><br></div>cuda=9.0 v141
???<br><div class="gmail_quote"><br></div><div class="gmail_quote"><br></div><div class="gmail_quote">My -Bv in test app outputs:</div><div class="gmail_quote"><br></div><div class="gmail_quote">1> C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.14.26428\bin\HostX86\x86\CL.exe: Version 19.14.26433.0<br>1> C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.14.26428\bin\HostX86\x86\c1.dll: Version 19.14.26433.0<br>1> C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.14.26428\bin\HostX86\x86\c1xx.dll: Version 19.14.26433.0<br>1> C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.14.26428\bin\HostX86\x86\c2.dll: Version 19.14.26433.0<br>1> C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.14.26428\bin\HostX86\x86\link.exe: Version 14.14.26433.0<br>1> C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.14.26428\bin\HostX86\x86\mspdb140.dll: Version 14.14.26433.0<br>1> C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.14.26428\bin\HostX86\x86\1033\clui.dll: Version 19.14.26433.0<br></div><div class="gmail_quote"><br></div><div class="gmail_quote">which if I interpret correctly (sadly with out my decoder rings) is not in <a href="https://blogs.msdn.microsoft.com/vcblog/2017/11/15/side-by-side-minor-version-msvc-toolsets-in-visual-studio-2017/">https://blogs.msdn.microsoft.com/vcblog/2017/11/15/side-by-side-minor-version-msvc-toolsets-in-visual-studio-2017/</a> <br></div><div class="gmail_quote"><br></div><div class="gmail_quote">as last entry is: <br></div><div class="gmail_quote"><br></div><div class="gmail_quote">VS2017, version 15.5 v141 in VS; version 14.12 1912<br></div><div class="gmail_quote"><br></div><div class="gmail_quote">Also from above<br></div><div class="gmail_quote"><br></div><div class="gmail_quote">
<span class="gmail-im"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>When
using MSVC 2017 and CUDA you will need to specify an explicit host side
compiler with -T version=15.## including the minor version ( <a href="https://cmake.org/cmake/help/v3.12/release/3.12.html#id3" target="_blank">https://cmake.org/cmake/help<wbr>/v3.12/release/3.12.html#id3</a> ).<br></div></div><div class="gmail-m_6830379022479796759HOEnZb"><div class="gmail-m_6830379022479796759h5"></div></div></blockquote></div></div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div></span></div><div class="gmail_quote">
would that be:</div><div class="gmail_quote"><br></div><div class="gmail_quote">version=19.14<br></div><div class="gmail_quote"><br></div><div class="gmail_quote">so putting it all together at -T line:</div><div class="gmail_quote"><br></div><div class="gmail_quote">
cuda=9.0 v141
version=19.14 <br></div><div class="gmail_quote"><br></div><div class="gmail_quote"><br></div><div class="gmail_quote">?</div><div class="gmail_quote"><br></div><div class="gmail_quote">Can we just skip to the future where we are defining compile settings in genetic code sequences?<br></div><div class="gmail_quote"><br></div><div class="gmail_quote">GCUACGGAGCUUCA</div><div class="gmail_quote"><br></div><div class="gmail_quote"><br></div><div class="gmail_quote">This is becoming a real monster anyway we may all want to just skip ahead to the punchline.<br></div><br></div></div>