In the cited version check from CUDA 9, it is clear that only MSC version up to and including 1911 are supported, while the latest MSVS update identifies as version 1912.

Version checks in header files, such as the one identified by the OP enforce the use of a supported tool chain. In case of problems with the CUDA tool chain, NVIDIA offers support only when CUDA is used with such a validated, a.k.a. The integration must then be validated, using a large-ish body of CUDA code. Tight integration with the host tool chain means that adjustments must be made to CUDA to adapt to new versions of the host tool chain. This was not deemed a particularly risky approach at the time, because in the early days of CUDA, when the ecosystem was tiny, new CUDA releases were shipped every four to five months on average, while host tool chains had new releases every one to two years. This tight integration creates dependencies of host header files for example. For those who object to my advice “Use a supported CUDA” version, let me explain why I believe that this is the only responsible advice.Įarly in the genesis of CUDA (2005-2006) a decision was made that CUDA should integrate into the most popular host tool chains as seamlessly as possible to create as little of a hurdle to adoption as possible.

Personally, I use a very old version of MSVS (2010) so I am not familiar with the toolset selection menu item you mention, but I assumed (maybe incorrectly) that MSVS 2017 users know how to operate the GUI IDE to select a tool chain version supported by CUDA. My statement addressed the poster’s issue directly, and you added useful detail. I am just a hobbyist CUDA user at this point. To avoid misunderstandings, please note that my presence in these forums is not part of any kind of professional activity.

Visual studio 9.0 beta program