wine-tkg-git VS wine

NTSync still seems to outperform any userspace fsync implementation https://github.com/Frogging-Family/wine-tkg-git/issues/936#i...

See: https://github.com/Frogging-Family/wine-tkg-git/issues/936

The exact version that I'm using: https://github.com/Frogging-Family/wine-tkg-git/actions/runs/4806748824

Clone the wine tkg git repo: git clone https://github.com/Frogging-Family/wine-tkg-git

Can't use native bcrypt.dll however Valve's proton uses a patched version. Wine-tkg uses Valve's version, might want to give it a try.

Sometimes when a detail of Windows isn't documented, the Wine source code can be useful. Have you tried looking at it for details of win64 SEH? For example:

https://github.com/wine-mirror/wine/blob/master/dlls/ntdll/e...

https://github.com/wine-mirror/wine/blob/master/dlls/msvcrt/...

Source code: https://github.com/wine-mirror/wine/tree/master/programs/wor...

It's Wine with some special sauce (Apple couldn't reuse VKD3D because they chose to invent Metal rather than stick with OpenGL/Vulkan so they had to build their graphics translation themselves). Crossover is built on the same technology. In fact, Apple's brew script literally links to Crossover's sources: https://raw.githubusercontent.com/apple/homebrew-apple/main/...

Things like the crypto API should be implemented if you can find the reference for your specific API calls here: https://github.com/wine-mirror/wine/tree/master/dlls/crypt32

Apple's version of Wine is aimed at developers, though. It shouldn't take too long for someone to make an app or script to easily set up environments with the developer runtime, but I doubt they'll support it as well as Valve supports Proton. If your application of choice doesn't need any fancy graphics, there's a decent chance Wine/Crossover can already run it anyway, no need to mess with Apple's SDK.

With the M2 Max outputting 28fps at 1080p (screenshot linked), I wouldn't expect too much from the gaming performance of this thing, though.

Not the OP, but Github's stats on https://github.com/wine-mirror/wine say the current Wine codebase is 95.1% C, 0.3% C++

Take a look at Wine's commit log. It's really well curated. https://github.com/wine-mirror/wine/commits/master

Fixes Overwatch 2 game freeze after a few seconds in game. After a long bisect it was found that wine-mirror/wine@4bf9d24 from upstream wine wine 7.13 and higher needed to be backported.

git clone https://github.com/wine-mirror/wine \ cd wine \ ./configure \ make \ make install \ wine ./Anomaly.exe

Well, I personally can't confirm nor deny that (the only "old" game I play is Plants vs Zombies (2009), and surprisingly it still works great with latest Proton). But the reality is that Wine/Proton are very large and complex projects, developed by pretty much just reverse engineering Windows; Couple this with the fact that a lot of changes happen in-between versions (especially in Wine), and even though an one-line change fixes an issue, it might end up breaking something, elsewhere. My point is, it's almost inevitable not to break stuff eventually. This is why Valve gives us older Proton versions to choose from.