![]() However, there is an extra check at compile time. Copy all files in that folder to your VS BuildCustomization folder (normally ‘C:\Program Files\Microsoft Visual Studio\2022\Community\Msbuild\Microsoft\VC\v170\BuildCustomizations’). From that folder, head to ‘visual_studio_integration\CUDAVisualStudioIntegration\extras\visual_studio_integration\MSBuildExtensions’. Note the path of the directory and open it in File Explorer. Launch the installer so that all files are exported to a temp directory. It does not install the full toolset, but will allow you to build your project. It’s unofficial (you guessed) and you will bypass version checks, so results will vary but it works for me for a 360 cam editing plugin for Davinci Resolve. Here is some help to get the CUDA SDK to work on VS2022. This seems to be an internal policy, but I still would appreciate if that policy could be ‘opened up’ a bit. What I also see is that they seem not to be allowed to make ‘forward-looking’ statements regarding the CUDA toolkit. That is actually one thing which can really contribute to the success of a framework (like CUDA definitly is) or not. Their support really saved my butt in a couple of occasion with difficult CUDA-related problems I had in the past. ![]() ![]() The support from NVIDIA people (robert etc.) and also from some non-NVIDIA people (njuffa, …) in this forum is excellent, in my experience. Well, I hoped also to get a bit more information when VS 2022 will be supported by CUDA toolkit.īut, actually I am quite sure that it will be supported by the next release of CUDA toolkit (11.6 ? 12.0 ?).įor recent Visual Studio versons, it always has been that way when I remember correctly.Īnd there is no question that they will support VS 2022 in the future (what would be the alternative on windows ivanov: I have to say the exact opposite than what you suggest. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |