• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Creating a CUDA Project in Visual Studio 2005

TheSpook

Limp Gawd
Joined
Feb 12, 2004
Messages
379
Hello all! I have an interest in graphics (experience with OpenGL, DirectX, Cg), and as such am interested in playing around with nVidia's newest toy CUDA.

The machine on which I've installed CUDA's SDK, Toolkit, and video card drivers is a Windows Vista Ultimate (64-bit) machine running an 8800GT.

Opening up the Solutions for the including demos in VS2005 works -- after a little finagling, they will all compile and run nicely.

However, when I try to create my own project, I receive an error stating that "cutil.h" cannot be found. I am using:
Code:
#include <cutil.h>
like the examples, so presumably the correct nVidia paths are set in PATH and LD_LIBRARY_PATH.

This is getting wordy.

"Can anyone provide a brief description of how I'd create my own CUDA project in Visual Studio?"
 
The easiest way is to use the supplied sample project from the SDK. :p

It's called template.sln under the "NVIDIA CUDA SDK\projects\template" folder. Delete the short sample code and it's ready for your code. There's not really a brief description since it would take many steps, but you can examine the project to see how it was made.

From the sound of it, you're probably missing $(CUDA_INC_PATH);./;../../common/inc from the include path (the last one is relative to the SDK projects\template folder). If you're missing anything else, just strip down template.sln and save yourself some time.
 
Thank you very much -- my include path was messed up. Suggestion worked well :)!
 
Back
Top