CODEWITHSUNDEEP
visual-studio-2010cudanvidiadirectoryproject-settings
sj755
sj755

Reputation: 4062

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?

Upvotes: 6

Views: 4880

Answers (1)

Simon Opelt
Simon Opelt

Reputation: 6201

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

Upvotes: 10

Related Questions