• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Unable to compile CUDA SDK samples on Windows

Community Beginner ,
Sep 30, 2020 Sep 30, 2020

Copy link to clipboard

Copied

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.

TOPICS
SDK

Views

474

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Contributor , Oct 01, 2020 Oct 01, 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.

 

Nathan_Lovell_52_0-1601591023270.png

Nathan_Lovell_52_1-1601591090443.png

 

-Nate

 

Votes

Translate

Translate
Contributor ,
Oct 01, 2020 Oct 01, 2020

Copy link to clipboard

Copied

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.

 

Nathan_Lovell_52_0-1601591023270.png

Nathan_Lovell_52_1-1601591090443.png

 

-Nate

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Oct 01, 2020 Oct 01, 2020

Copy link to clipboard

Copied

Hi Nate,

 

Exactly right.  Working fine now.

 

Thanks,

 

J.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Contributor ,
Oct 03, 2020 Oct 03, 2020

Copy link to clipboard

Copied

LATEST

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

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines