Skip to main content
jamesdean
jamesdean
Participant
September 30, 2020
Answered

Unable to compile CUDA SDK samples on Windows

  • September 30, 2020
  • 1 reply
  • 847 views

Hi,

 

I'm struggling to get either the vignette, or CrossDissolve samples to build on windows 10. I'm using Premiere CC13 Windows SDK.

 

It looks like the build fails at the custom build stage of the .CU files.  I was originally using CUDA SDK v11.1 but this was failing because of the arch=sm_30 argument in the custom build instruction.

 

Dropping back to CUDA SDK v10.2 resolves the architecture failure, but I'm seeing this in the build output in VS2019:

 

1>------ Build started: Project: Vignette (GPU), Configuration: Debug x64 ------
1>Converting PiPL for Vignette
1>Microsoft (R) C/C++ Optimizing Compiler Version 19.23.28106.4 for x64
1>Copyright (C) Microsoft Corporation. All rights reserved.
1>
1>Vignette.r
1>Building Vignette.cu
1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets(230,5): error MSB6006: "cmd.exe" exited with code 1.
1>Done building project "Vignette.vcxproj" -- FAILED.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

 

Digging deeper on that error looks like the build is failing because the custom build stage returned an error.

 

Any ideas?

 

Thanks,

 

James.

This topic has been closed for replies.
Correct answer Nathan Lovell_52

James,

 

This is likely because of an incorrect MSVC version in your .cu compile options. Sometimes by default it can put in the wrong version of this, so double check which version you have installed and update the .cu file.

 

 

-Nate

 

1 reply

Nathan Lovell_52
Nathan Lovell_52Correct answer
Inspiring
October 1, 2020

James,

 

This is likely because of an incorrect MSVC version in your .cu compile options. Sometimes by default it can put in the wrong version of this, so double check which version you have installed and update the .cu file.

 

 

-Nate

 

jamesdean
jamesdeanAuthor
Participant
October 2, 2020

Hi Nate,

 

Exactly right.  Working fine now.

 

Thanks,

 

J.

    Nathan Lovell_52
    Nathan Lovell_52
    Inspiring
    October 3, 2020

    Glad it worked, please mark as the answer so others can find the issue!

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices