Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Issue with production release of CUDA Toolkit 4.0 and Nsight 2.0

I previously had the release candidates of both programs, then I uninstalled them and installed the production releases of the programs. This includes the CUDA toolkit, Parallel Nsight, and the GPU computing SDK. When I go to Project->Build Customizations and select CUDA 4.0, I am no longer able to set the .cu file as a CUDA C/C++ file, and when I try reloading the project, I get an error that reads:

The result "" of evaluating the value "$(CudaBuildTasksPath)" of the "AssemblyFile" attribute in element <UsingTask> is not valid. C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\BuildCustomizations\CUDA 4.0.targets

What is the issue here?

like image 449
sj755 Avatar asked May 27 '11 18:05

sj755


People also ask

Is Cuda Toolkit free?

Install the free CUDA Toolkit on a Linux, Mac or Windows system with one or more CUDA-capable GPUs. Follow the instructions in the CUDA Quick Start Guide to get up and running quickly.

How do I update Cuda Toolkit?

Check/Update driver version One simple way is to open Ubuntu Software app, choose Software & Updates, and click Additional Drivers. That's where you can see a list of driver versions you can choose to use, including the specific version you are using.

Why do we need Cuda Toolkit?

With the CUDA Toolkit, you can develop, optimize, and deploy your applications on GPU-accelerated embedded systems, desktop workstations, enterprise data centers, cloud-based platforms and HPC supercomputers.

What is the Nvidia Cuda Toolkit?

The CUDA Toolkit from NVIDIA provides everything you need to develop GPU-accelerated applications. The CUDA Toolkit includes GPU-accelerated libraries, a compiler, development tools and the CUDA runtime.


1 Answers

The handling of the extension/build task properties seems to have changed. (It has for me coming from cuda 3.2, nsight 1.5, vs 2010)

I was able to resolve the issue by fixing/changing the vcxproj file:

look for

  <ImportGroup Label="ExtensionSettings" />

or

  <ImportGroup Label="ExtensionSettings">
  </ImportGroup>

replace with

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

Just a quick update: NVIDIA provides a fix at their developer pages. Look for CUDA Toolkit 4.0 Build Customization BUG FIX Update

like image 142
Simon Opelt Avatar answered Sep 19 '22 10:09

Simon Opelt