3 ms·

The code weaver approach doesn’t sound like something like hat is accessible to small time people... did they have to build their own thunking layers? Sounds

The code weaver approach doesn’t sound like something like hat is accessible to small time people... did they have to build their own thunking layers? Sounds like it’s easier to rebuild as a Win32 and have OS X users use wine then. I know a company the size of Apple can’t be expected to be some kind of stable dev platform like how Microsoft treats Windows where I can still run Win32 stuff from 1993 on Windows 10 x64. Maybe one day Apple might take an interest in the desktop again but it seems so unlikely.

skissane 6y ago
> The code weaver approach doesn’t sound like something like hat is accessible to small time people... did they have to build their own thunking layers? It wasn't easy, no. They had to do two things: 1) Fork clang and extensions to C to support mixed 32-bit and 64-bit address spaces 2) Get a special code-signing entitlement from Apple allowing them to call the API to enable 32-bit code execution (not required if you are okay with disabling SIP) Lots of technical details here: https://www.winehq.org/pipermail/wine-devel/2019-December/156602.html https://www.winehq.org/pipermail/wine-devel/2019-December/15... Yeah, this is a monumental effort that few other than Codeweavers could replicate, and I believe they got some help from Apple engineering to do it. They've open sourced their code, but they aren't upstreaming it into mainstream Wine – having to use a forked C compiler is just a bit too much.