Catalina and the future of Wine on Mac

[Gcenx]

This sounds like a few months months work - just to get a Wine 64 bit .pkg to run 64 bit Windows apps?

Thanks for your help.

If your only wanting to run win64 applications you can do so already on macOS Catalina, the issue is win32 applications.

Personally been running from a self compiled version of CrossOver-19 since the source hit already moved over to CrossOver-19.0.1 aka WineCX19.0.1 for a while now, while I could be provided the issue is needing to have SIP disabled for wine32on64 to function without it being code signed & notarized.

I'd considered making a brew tap/cask to download and install a custom "Wine Crossover" bundle I've built that functions on OS X 10.8 > macOS Catalina but the requirement of having SIP disabled would end up causing me more of a headache.

[starparrot]

If your only wanting to run win64 applications you can do so already on macOS Catalina, the issue is win32 applications.

It just seems to be a bit of work and I'm not a Wine expert. I was hoping for a simply 64 bit .pkg.

Personally been running from a self compiled version of CrossOver-19 since the source hit already moved over to CrossOver-19.0.1 aka WineCX19.0.1 for a while now, while I could be provided the issue is needing to have SIP disabled for wine32on64 to function without it being code signed & notarized.

I imagine this would involve me purchasing Crossover, which I don't have a licence for.

Thanks.

[Gcenx]

It just seems to be a bit of work and I'm not a Wine expert. I was hoping for a simply 64 bit .pkg.

Not really if you install homebrew

Code: Select all

brew cask install xquartz
brew cask install (wine-stable/wine-devel/wine-staging)

Now you have wine64 within a stock terminal session, so you can use things like
wine64 explorer
wine64 winecfg
wine64 wineboot
etc

I imagine this would involve me purchasing Crossover, which I don't have a licence for.

You only purchase a CrossOver license if your going to be using their product.
Using wine compiled from their source is a different matter, unless you don't want to have SIP disabled then by all means make a purchase the product is good.

[azoreseuropa]

Does that mean Wine will never run on Catalina at all. never ? Thy are not working on Wine that will run on Catalina ?

[Gcenx]

Does that mean Wine will never run on Catalina at all. never ? Thy are not working on Wine that will run on Catalina ?

I guess you haven’t read anything within this thread as it’s been explained multiple times now.

Current Winehq releases won’t function on macOS Catalina, CrossOver-19 and above do function on macOS Catalina.

So yes they are working in getting something functional on macOS Catalina it’s called wine32on64.

Your current options are as follows;
- Purchase CrossOver-19.0.1
- Downgrade to macOS Mojave (use all Winehq releases)
- Compile crossover-wine source (disable SIP to run it)

[azoreseuropa]

No, I didn't. And I thank you for your time to write it to me. Good day.

[markwozere]

Does that mean Wine will never run on Catalina at all. never ? Thy are not working on Wine that will run on Catalina ?

I guess you haven’t read anything within this thread as it’s been explained multiple times now.

Current Winehq releases won’t function on macOS Catalina, CrossOver-19 and above do function on macOS Catalina.

So yes they are working in getting something functional on macOS Catalina it’s called wine32on64.

Your current options are as follows;
- Purchase CrossOver-19.0.1
- Downgrade to macOS Mojave (use all Winehq releases)
- Compile crossover-wine source (disable SIP to run it)

I don't suppose we have any timeframe predicted for wine32on64 yet?

[Gcenx]

I don't suppose we have any timeframe predicted for wine32on64 yet?

We won’t see wine32on64 until after CrossOver-20 but this doesn’t mean it will become part of upstream wine.

As wine32on64 still requires a custom compiler Julliard doesn’t want to include wine32on64 patches into upstream, I can see this changing after the custom compiler is no longer required.

This was all mentioned on the wine-devel mailing list when DarkShadow (a wine/winetricks contributor) asked for more information, this happened a little after I’d already reached out for more clarification on some build issues I was having when using my build system over a minimum setup.

Right now wine32on64 needs a lot of features set to disabled in order for it to compile.

[markwozere]

I'll downgrade back to Mojave in that case for the time being

[Gcenx]

I'll downgrade back to Mojave in that case for the time being

That’s currently the best option if the Mac supports it.

You might wanna check my GitHub repository macports-wine using that you can build wine-stable(wine)/wine-devel/wine-staging & wine-crossover just apply the provided patch using sudo to force macport to allow +universal on Mojave and add the 10.13 SDK into the location I mention.

Now you can install the most recent version of wine with things like MoltenVK, gnutls, gstreamer and evening FAudio with wma audio if you build using +ffmpeg flag.

It also include two custom ports for shared wine-mono and wine-gecko that also works with Winehq Wine-5.x releases.

[Gcenx]

Delete me