https://bugs.winehq.org/show_bug.cgi?id=52528
--- Comment #5 from Alois Schlögl alois.schloegl@gmail.com --- (In reply to Sveinar Søpler from comment #4)
(In reply to Alois Schlögl from comment #3)
But if this works out, the workaround is to use wine-staging, and this bug report would become moot.
Since nvCUDA is a windows low-level library - much like libcuda would be for Linux - you cannot expect the windows version to work by installing that. It is somewhat similar for other things like OpenCL. You cant install some windows driver in wine and expect this to work.
Sure, I understand. Some reports seem to suggest that this was possible with cuda 9.x . And when I started to look into this, I was not aware that wine-staging is the proper way of running cuda applications. That's something I learned now.
Wine-devel does NOT include nvCUDA, so if you do not build/install nvcuda standalone and install it, you have to use wine-staging. There are workarounds to this, but i will not go indepth into this here.
Not sure what you mean by "installing over ssh" tho?
I was trying to install warpem on a remote machine, and had difficulties installing dotnet472. The messages from "winetricks dotnet472" were different when I did not use X-tunneling, and this was puzzling me. (Now, I know these difficulties were related to a lack of diskspace and perhaps the winetricks versions).
Afterall, I've been able to get warpem running https://appdb.winehq.org/objectManager.php?sClass=version&iId=40620
Your hints were important in getting this to work. Thanks.