https://bugs.winehq.org/show_bug.cgi?id=51541
Sveinar Søpler cybermax@dexter.no changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |cybermax@dexter.no
--- Comment #2 from Sveinar Søpler cybermax@dexter.no --- (In reply to Liam Middlebrook from comment #0)
I've attached a patch which fixes this issue and lets me launch CUDA applications from Steam.
Thank you Liam. I can confirm this works for using PhysX/Cuda for games like Batman Arkham Knight under steam/proton.
This would also be the case for nvencodeapi and nvcuvid if it were to be used under steam/proton. I am not aware of any usecases atm tho.
(In reply to Zebediah Figura from comment #1)
This is only a hack working around the real problem with the patch set. We should be using WINE_CHECK_SONAME like everything else.
That would be dependent on libcuda being installed at configure-time tho won't it? Probably not too hard to achieve...
Though it's really worth examining whether we really want nvcuda in upstream Wine; and, if not, we should remove it from wine-staging.
There are many usecases for having this upstream tho. What is the best argument for scratching this altogether?