Interestingly, it works correctly for the Samples_vs2017 solution, but not for File->New Project->CUDA 9.1 Runtime. I can’t spot the relevant difference in the configurations. I am using the 2016 (v140) Platform Toolset for both cases. Anyway… I can edit the code, hit F5, and it will run the las…

This issue is also affecting me. A new CUDA project will only compile the CUDA kernel with a Ctrl+F7 or solution rebuild. Making changes to the code and hitting F5 or F7 won’t compile the changes.

I have filled bug #2396234 for this issue.

I think this is caused by a change in VS 2017: [image] Visual Studio Feedback Visual Studio Feedback “…as VC build Up-To-Date check solely relies on read and write tlog files created during build and not checking project items any more.”

Microsoft says they changed the up-to-date check in VS 2017, so it is up to Nvidia to change their CUDA integration: [image] Visual Studio Feedback Visual Studio Feedback

Yes, its being worked on internally as a result of the bug filed that was mentioned in one of the previous comments in this thread.

Thanks Robert. I tried to adjust the custom CUDA 10.0.targets but could not get it to work. My rant to Microsoft is included (from Visual Studio Feedback ): "While Olga’s “suggestion” is obviously correct, the required action is next to impossible! There is very little documentation on this vital …

@Robert_Crovella Any info about the ETA of the fix. We badly need an improved MSBuild integration. Does someone have a workaround with GetOutOfDateItems mentioned here? [url] Visual Studio Feedback

Edit: Not working correctly! See improved solution later. I managed to find a workaround: In the CUDA 10.0.targets files: “C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\VC\VCTargets\BuildCustomizations\CUDA 10.0.targets” “C:\Program Files (x86)\MSBuild\Microsoft.Cp…

Can confirm the above solution works. For me, I only had the first file and it was enough. Cheers!

Hi chrispy81, Thanks for sharing the information. This works okay for us too, although it seems to somehow require some weird sequence of actions before it’s effective for all .cu files in a project. As if one “previous” failure per .cu file is required before it starts working. Cheers!

Visual Studio 2017 not detecting changes in CUDA .cu files

Accelerated Computing CUDA CUDA Setup and Installation

Abraham_Martin August 26, 2021, 2:56pm 38

I managed to solve this editing the .targets file installed by NVIDIA, but now VS is not able to add any dependencies of the .cu (includes) to the tlog files, so if I change any .cu header, I need to force rebuild all my .cu files, which is quite time consuming.

Topic		Replies	Views
Because of the slightest change in CU/CUH files, you need to re-compile whole solution, how to configure the partial compilation? CUDA Programming and Performance	0	518	December 15, 2017
How to add a cuda-file to VS 2015 c++ solution CUDA Programming and Performance	28	24439	August 20, 2017
CUDA 9 Unsupported Visual Studio Version Error CUDA Setup and Installation	61	77385	September 17, 2018
Cuda 10.1 forces all .cu files to be recompiled after adding one file in the visual studio 2017 proj... CUDA Setup and Installation	0	658	November 9, 2019
CUDA 9 failed to support the latest Visual Studio 2017 version 15.5 CUDA Setup and Installation	56	61061	September 22, 2018
How to tell Visual Studio to build .cu files CUDA Programming and Performance	4	10851	October 23, 2018
Changes in defines are not seen by studio F5 (debug-run) Nsight Visual Studio Edition	7	1785	December 20, 2013
Compiling Nvidia CUDA 10.1 in Visual Studio 2019 (Enterprise) project Fails Nsight Visual Studio Edition	21	12006	October 3, 2021
CUDA Toolkit 10.0 and Visual Studio CUDA Programming and Performance	0	1059	September 25, 2018
CUDA examples fail in visual studio CUDA Setup and Installation	2	1909	July 15, 2019

Visual Studio 2017 not detecting changes in CUDA .cu files

Related topics