after installing the SDK on Visual Studio 9, and working through a couple of listings from “Cuda by Example”, I noticed that the types used by Cuda
(e.g. cudaError_t) cannot be accessed through VS’s “Go to Declaration” or “Go to Definition”. I presume that the nvcc compiler adds a lot of header files that contain these, and that they are hidden from Visual Studio before that.
Am I correct in this assumption, and is there any tooling to turn source-code-navigation on for these types?
Another issue: Code folding and brace matching are broken. I managed to get syntax highlighting to work, but that seems to be all of the luxury. Even the conventional code can no longer be navigated with F12, as I noticed. This is like the eighties!
Yeah the installation on my PC has this problem too, I suspect it’s some sort of path problem.
I just tried to figure it out in an ms-dos prompt the following happened:
Without quotes:
C:\Users\Skybuck>%CUDA_PATH%
‘C:\Tools\CUDA\Toolkit’ is not recognized as an internal or external command,
operable program or batch file.
With quotes:
C:\Users\Skybuck>“%CUDA_PATH%”
‘"C:\Tools\CUDA\Toolkit 4.0\v4.0"’ is not recognized as an internal or external
command,
operable program or batch file.
Notice how the first one seems to be incomplete, it’s because there is a space in the folder.
Perhaps this is causing Visual Studio to not find these include files ?!?
Hmmm, strangely enough at the moment it is working… don’t know if it was something I did… might be because my virtual drive had “lucky” drive letter assignments…
