Using CUDA with Visual Studio 2017

by
  1. If you want to install CUDA 8.0 with Visual Studio 2017 you need to install additional components for Visual Studio 2017.

    Click on the Start Menu and type Visual Studio Installer. Open Visual Studio Installer

    Open Individual components tab and select VC++ 2015.3 v140 toolset

    under Compilers, build tools and runtimes.

install additional components for Visual Studio 2017

  1. You also need to install .NET Framework 3.5 if you didn’t have it installed.
    Nvda.Build.CudaTasks.v8.0.dll assembly dependents on MS .NET Framework 3.5.

Open Classical Control Panel, go to Programs and features
and press Turn Windows features on or off. Check .NET Framework 3.5 and press OK.

enter image description here

  1. Download full CUDA toolkit distribution and extract it somewhere on your disk.
  2. If you didn’t have CUDA toolkit installed, do it now. If you have only Visual Studio 2017 installed, unselect Visual Studio integration checkbox.

Now you want to receive the "No supported version of the visual studio was found" error.

But in order to successfully build Cuda toolkit projects in Visual Studio 2017, you also need to follow steps 5 and 6.

  1. Go to the CUDAVisualStudioIntegration\extras\visual_studio_integration\MSBuildExtensions
    folder in your extracted distribution, copy all the files and paste them to
    C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\v140\BuildCustomizations:

msbuild

  1. In the last step, you will need to edit your Cuda projects to recognize NVidia’s build tasks from Visual Studio 2017. Open your .vcxproj file in a text editor and find all occurrences of CUDA 8.0.props. Replace the macro at the beginning of the string with $(VCTargetsPath14) so that XML snippet would look as follows:

<ImportGroup Label="ExtensionSettings">
<Import Project="$(VCTargetsPath14)\BuildCustomizations\CUDA 8.0.props" /></ImportGroup>

Don’t forget to edit the custom targets path at the end of the file:

<ImportGroup Label="ExtensionTargets">
<Import Project="$(VCTargetsPath14)\BuildCustomizations\CUDA 8.0.targets" /></ImportGroup>

Make sure to double check your path conifuration!

If you use nvcc from command prompt you might not be calling cl.exe from Visual Studio folder!

another cl.exe might be in path

Now you can build your Cuda project from Visual Studio 2017.

Parts of this solution are from Oleg Tarasov blog.

More Related Contents:

  1. Get Visual Studio to run a T4 Template on every build
  2. Using Git with Visual Studio [closed]
  3. Where does Visual Studio 2017 store its config?
  4. nvidia-smi Volatile GPU-Utilization explanation?
  5. What is the purpose of the Visual Studio Hosting Process?
  6. Open a file in Visual Studio at a specific line number
  7. CUDA how to get grid, block, thread size and parallalize non square matrix calculation
  8. Any particular function to initialize GPU other than the first cudaMalloc call?
  9. RunAs A different user when debugging in Visual Studio
  10. How do you use the Immediate Window in Visual Studio?
  11. Project reference VS NuGet
  12. Unblocking a DLL on a company machine. How?
  13. Avoiding “Press any key to continue” when running console application from Visual Studio
  14. How performing multiple matrix multiplications in CUDA?
  15. Break in Class Module vs. Break on Unhandled Errors (VB6 Error Trapping, Options Setting in IDE)
  16. How to turn off CodeLens-References
  17. What does “Register for COM Interop” actually do?
  18. Break when a value changes using the Visual Studio debugger
  19. Visual C++: How to disable specific linker warnings?
  20. MS-Build 2017 “Microsoft.WebApplication.targets ” is missing
  21. Green Bars in Visual Studio 2010
  22. How to make visual studio break only on unhandled exceptions?
  23. Best Practice for Git Repositories with multiple projects in traditional n-tier design
  24. How to fix “Internal Diagnostics Hub Exception” in VS 2015 Update 1?
  25. Visual Studio isn’t tracking changes, or checking out files from source control as I edit them
  26. How does CUDA assign device IDs to GPUs?
  27. Visual Studio open files question
  28. Recommended number of projects in Visual Studio Solution
  29. 500 Error Running Visual Studio ASP.NET Unit Test
  30. Structuring projects & dependencies of large winforms applications in C#

Leave a Comment