First of all , i have the following specs:
-Visual studio 2015Pro version: 14.0.25123.00 update 2
-Nvidia GeForce GTX 765M (i know it is not in the supported gpus list)
-Nsight 5.1 and Nsight 6.0 installed
-CUDA toolkit 8.0 installed
-Nvidia Driver version : 416.16 installed
-Microsoft Windows 10 64bit
My problem is that Nsight menu is missing in Visual Studio and I'd like to start CUDA debbuging.
The things that I have tried:
First I have installed Nsight 6.0 then 5.1 (i restarted my PC) still missing Nsight menu(I actually can't find Nsight in my VS Extensions and Updates box).Then updated to the latest Nvidia Driver(I have read the manual of it but I could not find if it is CUDA debugging capable).
My visual studio is installed on X:\ drive but I have the following shortcuts pointing to where Nsight is located on C:\
Shortcuts I've read in a different topic I must have these.
The story behind it:
I am developing a filtering program which is not working properly , I have followed the steps the program makes but I need to use the debugger.
At this point I am asking for some help.
I have updated my VS2015 to update3 also installed CUDA toolkit 10 and now the nsight menu is showing.
Related
I want to develop a program using CUDA but I am getting lost by install instructions on NVidia's site.
So here is what I have:
Windows 10 laptop with a NVidia GPU GeForce GTX 870M
(both OS and GPU driver are up to date)
Visual Studio 2017, Version 15.8 (also up to date) _MS_VER=1915
On this webpage, I found out that my GPU is CUDA enabled (good news) with "Compute capability" 3.0. What does it mean?
I know that CUDA versions are sensitive to the version of Visual Studio used, so
my question is simple:
what version of CUDA should I download and install? and can I build and run programs with my version of Visual Studio?
As far as I know, no version of the CUDA Toolkit currently supports Visual Studio 15.8. The latest CUDA 9.2 supposedly supports up to Visual Studio 15.6. Note that the issue of Visual Studio support really only concerns the NVCC compiler and Visual Studio Integration. There's nothing preventing you from, e.g., using the CUDA Driver API with whatever compiler you wish (including the latest version of VS).
One way around these issues used to be to put your CUDA code into a separate static library, build that with the VS 2015 compilers, and link it to the main project which could be built using VS 2017.
Make sure you have selected the VC++ 2015.3 v14.00 (v140) toolset for desktop package in Visual Studio Installer:
You can then switch the toolset to use for each project in Project Properties > General:
Unfortunately, I've recently encountered some issues with linking binaries built with VS 2015 to binaries built with the VS 2017 15.8 compilers, so that path might no longer work (seemed to be related to the new "Just My Code Debugging" feature). But then, binary compatibility across compiler versions was never really something to rely on in the first place…
Another solution would be to downgrade your Visual Studio to 15.6.
The compute capability of a device basically tells you what generation of GPU architecture you're dealing with and which features you can rely on. Or in the words of the CUDA Programming Guide:
The compute capability of a device is represented by a version number, also sometimes called its "SM version". This version number identifies the features supported by the GPU hardware and is used by applications at runtime to determine which hardware features and/or instructions are available on the present GPU.
More details on individual compute capabilities/architectures can be found, e.g., here.
Recently I installed Visual Studio 2017 Enterprise along with WDK 10 for 1709 My workloads contained C++ workload. . My machine is a Windows 8.1 Pro with net framework 4.6.1. After installing the WDK I expected the templates to come in the Legacy section of Visual C++ but no legacy option is present in it. I don't understand what is the problem. Please help me.
Thanks in advance
I resolved the issue. It was due to a missing windows 10 SDK. Reinstallating the WDK with appropriate SDK solved the problem
Developing drivers to windows is quite interesting one will be exposed to advanced Operating System Concepts. The set up for the environment will be IDE
IDE - Visual Studio (https://visualstudio.microsoft.com/thank-you-downloading-visual-studio/?sku=Community&rel=16)
Compilers (WDK)
Debugger (WDK)
WDK contains both(https://go.microsoft.com/fwlink/?linkid=2085767). Latest Visual Studio(VS2019) will come along with the latest WDK(10, 1903 as of now).
Sometimes plugins might not work properly i.e integration issues between Visual Studio and WDk.
By going to the location "C:\Program Files (x86)\Windows Kits\10\Vsix\VS2019" and run VSIX installer.
Now in a new project, driver related templates are available.
Just installed latest Visual Studio 2017 Preview 15.6 and CUDA Toolkit 9.1
Created new CUDA demo project and tried to compile, but got bunch of errors, one of them:
cannot open source file "stddef.h"
cannot open source file "stdio.h"
unsupported Microsoft Visual Studio version! Only the versions 2012, 2013, 2015 and 2017 are supported
Did anyone try to work with CUDA 9.1 in VS 2017 Preview?
As per advises from Robert and NVidia DevTalk forum in order to compile project I need to:
Install Visual Studio 2017.4 from here
https://www.visualstudio.com/en-us/productinfo/installing-an-earlier-release-of-vs2017
Reinstall CUDA
or
Add Visual Stodio 2015 Toolset to existing VS 2017 installation
Reinstall CUDA
Change project properties to use older toolset
I was able to get CUDA 9.1.85 to build with VS 2017 15.4.
I first uninstalled all previous VS instances and then reinstalled VS2017, making sure to go to "individual Components" and selecting VS 2015 Toolset.
I then used the Step A suggestion from #oregonduckman in this post and used the standard VGA driver for my display adapter (video card).
I then killed every NVIDIA process and manually deleted every NVIDIA folder on my machine.
Finally, I installed CUDA 9.1.85 including the VS Integrations which also reinstalled my display adapter driver that I had manually removed. I was then able to build all of the CUDA samples.
I suspect that the issue lays with either the VS Toolset is unsupported by CUDA 9.1 or there was an incompatibility between VS and my NVIDIA driver somehow.
Btw, I am running Windows 10 Pro with a GTX 780 card.
I do the following to fix the problem on VS 2017 Enterprise:
Open VS 2017--> Tools --> Get Tools and Features --> Add Visual Studio 2015 (v140) Toolset and Windows SDK Version 10.0.15063.0
Reinstall CUDA
Right click on the project --> Properties --> Configuration Properties --> General --> Set target platform version to 10.0.15063.0 and set platform toolset to Visual Studio 2015 (v140)
For the past few days I have installed many versions of visual studio, but nothing is picked up by CUDA 7.5:
I am on windows 7, what could be the issue?
EDIT: I have versions of Visual Studio that CUDA 7.5 asks for, please refer to the image for what versions I have installed.
In your installed programs, more precisely in the screenshot you provide, it seems you have the redist packages but not Visual Studio itself.
Did you really installed Visual Studio ?
Do you know the big difference between the redist packages and the integrated development environment itself ?
Plus, it seems by now Visual Studio 2015 is not yet supported.
See this page on the documentation from Nvidia.
I´m trying to install sdk of open cl sdk of Intel in my machine to use in Visual Studio 2010 or 2012, but when I install, the instalation rollback and didn´t install when I select to integrate with any version of Visual Studio, but if I didn´t select any option to integrate it install.
So I need to use this in Visual Studio for my class.
I changed the permission folder in Windows 8 and it didn´t works.
I´m using windows 8 single language 64 bits, actually using Visual Studio C++ Express 2010.
I just read a blog post on a similar topic. The fix there might work for you as well. I haven't tried it myself since I'm not having this problem.
Please see: https://anteru.net/2013/11/01/2204/
In this case the blogger was not able to install the latest Intel OpenCL SDK after upgrading to Windows 8.1