I'd like suggesting to merge the 17 patches from wine-staging/patches/nvcuda-CUDA_Support patches into upstream wine for the following reasons:
Currently Cuda applications for Windows do not run in native Wine. Such an application is Warpem (available for Windows only), and CUDA-Z for Windows. I assume there are other applications as well. This could be fixed by pulling in the 17 patches wine-staging/patches/nvcuda-CUDA_Support.
Possible disadvantages: - build dependency to cuda - some distros might not want to have a build dependency on cuda.h That's the choice of the package manager, but this should be endorsed and recommended for the above reason.
- run-time dependency on cuda wine does not have a runtime dependency on cuda (probably due to dynamic linking) e.g. cuda-z can be started under wine, and stops gracefully with a message the cuda is not available.
- number of APIs to maintain is currently done anyway (by the wine-staging team)
From a the perspective of some application, Cuda is part of the operating system should be provided by the platform (Wine in our case). Overall, it seems merging the nvcuda-CUDA_Support into upstream Wine are the right thing to do.
Best regards, Alois