[CMake] Missing <target>_EXPORTS definition in CUDA host compilation

[Hancox, James]

Hi Brad,

I swapped out CUDA 8.0.44 for CUDA 8.0.61, and my problem magically went away. Thanks a lot for the help, I never would have made that connection! 

I checked the .vcxproj file before regenerating, and the _EXPORTS define was right where it should be, so it definitely seems like a bug in the VS plugin. We previously used FindCUDA (which doesn't use the plugin) and never ran into that problem, so I hadn't even considered it as a possibility. It might be worth adding a warning/diagnostic to let people know that 8.0.44 has bugs in the VS integration? Will probably save you a lot of similar bug reports in the future. 

Thanks again,
James 

-----Original Message-----
From: Brad King [mailto:brad.king at kitware.com] 
Sent: 20 June 2017 14:42
To: Hancox, James <JHancox at tmvse.com>
Cc: Robert Maynard <robert.maynard at kitware.com>; cmake at cmake.org
Subject: Re: [CMake] Missing <target>_EXPORTS definition in CUDA host compilation

On 06/20/2017 06:03 AM, Hancox, James wrote:
> https://github.com/jameshancox/cmake_example_16993

Thanks for the example.  Also, thanks for trying the release candidate!

> Visual Studio Professional 2013 Update 5 CUDA 8.0.44 cmake 3.9.0.rc3

I'm not able to reproduce it using VS 2013 Update 5, CMake 3.9.0-rc3, and CUDA 8.0.61.  Only the CUDA version is different.

IIRC we did encounter some problems with preprocessor definitions not being properly used by the CUDA VS Integration while developing the support in CMake.  Upgrading from CUDA 8.0.44 to 8.0.61 fixed them.

Please verify that the definition appears in the .vcxproj file.
If so, then please try updating your CUDA version.

Thanks,
-Brad


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com ______________________________________________________________________

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________