Wine 6.0
source.winehq.org
source.winehq.org
Still very disappointed that macOS has not been supported since Catalina (10.15) dropped 32-bit support - from my understanding, the 32-bit architecture is deeply integrated into Wine and removing it would be a significant effort. Understandably the focus has always been on Linux, but I would still appreciate at least an update from the team on potential macOS support in the future.
And it seems possible to build CrossOver wine from sources: https://github.com/Gcenx/homebrew-wine
"This release is dedicated to the memory of Ken Thomases, who passed away just before Christmas at the age of 51. Ken was an incredibly brilliant developer, and the mastermind behind the macOS support in Wine. We all miss his skills, his patience, and his dark sense of humor."
Wine developers said in the past, that they were considering dropping macOS support altogether because of issues like that.
They could be emulated using compute shaders, but MoltenVK does not do this at the moment. Animations work properly inside Windows VM through Parallels, so I guess this is what their proprietary driver does.
Apart from that I played Witcher 3, Sekiro and Dark Souls through CrossOver with no issues and very solid performance on basically the weakest ARM Mac that will ever exist.
But I of course agree that Linux is much better option for gaming.
So you had x64 binaries calling a DX API that called a Vulkan API that called a Metal API all on top of a JIT translation layer to ARM on two month old hardware and it worked well?
That’s fucking incredible, man.
Absolute insanity how well tooling has evolved.
> M1 MacBook Air
I think you may have missed the point :P
Is there a way to get Wine as a single binary / docker or something that is easy to install?
Edit: As for why it was really difficult is because of that: https://wiki.winehq.org/Debian ( The WineHQ packages for Debian 10 and later require libfaudio0 as a dependency. Since the distro does not provide it for Debian 10, users of that version can download libfaudio0 packages from the OBS. See https://forum.winehq.org/viewtopic.php?f=8&t=32192 for details. ) That bloody libfaudio0.
It's a launcher that manages the dependencies needed for each individual application (setting up dedicated wine prefixes, installing any dotnet packages, etc)
Install it, then use the appropriate install script from the website: https://lutris.net/games/diablo-ii/
Just wanted to point that out before anyone sees this great project and decides to contribute a script to an unknown game.
According to https://wiki.debian.org/Wine however it should on x86_64 in theory be as simple as the following in order to install both the 64 and 32-bit versions:
sudo dpkg --add-architecture i386 && sudo apt update
sudo apt install \
wine \
wine32 \
wine64 \
libwine \
libwine:i386 \
fonts-wine
Notice in particular the dpkg --add-architecture i386. This enables multiarch.Edit, apparently Debian 10 is buster rather than bullseye, which makes me wonder, why have you not upgraded?
https://wiki.winehq.org/Debian
And as a side note, better don't use Debian stable for gaming. It's not a desktop distro. Debian testing / unstable is a way better option.
Tribes 2 and Test Drive 5 work great with Wine and are fun to tinker with even though they are 20+ years old now.
Proton being the name of the wine fork by valve.
On average I don't expect specific merits using Proton vs using vanilla Wine for non-game applications. As far as I know, Proton-specific patches are usually hacks targeted either generally at games or at specific titles. Actually, using Proton could be worse than vanilla Wine, because Proton is based on a past version of Wine which only gets updated every now and then (last Proton is based on Wine 5.13), so you are missing some development (on the other hand, sometimes developing features breaks stuff, so this could also go the other way around).
Ideally, we always want as many patches as possible to go into vanilla Wine instead of Proton or CrossOver; first because we love free software and second because maintaining forked versions is time-consuming like mad. However Wine rightly has strict code quality requirements, and sometimes developing a proper fix for some bug is either impossible or too long; those cases are handled with patches in Proton (perhaps shared with Wine Staging or CrossOver).
Disclosure: I work for CodeWeavers on Proton. Opinions my own.
CrossOver and Proton are rather independent as codebases, except they're both constantly rebased on Wine. Of course patches can flow in both directions (and from either to vanilla Wine, which is the best), but AFAIK none is systematically based on the other.
I’ve always been curious, I stopped playing games shortly before steam on Linux, back then it was a mess of using various wine versions and configs on various games (or maybe I just sucked, I had far less luck getting stuff to work than others on Wine DB).
There are also some instances of game-specific behaviour: Proton detects at runtime which game is running and decides whether to enable or not some code. This is done for the most filthy hacks that are required to run something, but risk to spoil some other program. Search the code for instances of getenv("SteamAppId") or getenv("SteamGameId").
- wine with some additional patches (written by Codewavers themselves so they will make it to wine proper)
- DXVK and its DX12 counterpart for better direct X compat (these work fine with wine, but they are not part of wine)
- Some bridging layer to let wine programs talk with native Steam (previously you would have had to run Steam itself under wine)
You can run other programs under proton by adding them to Steam, but probably not worth it for non games.
[0] https://www.gamingonlinux.com/articles/codeweavers-on-how-pr...
I can't see why a third-party program cannot be used with Proton. You can just add it as an external program and enable windows compatibility as you would with a steam game.
So yes, please leave reports, they will get addressed, eventually. :-)
Can someone give us a bottom line with respect to, say, the ability to run MS Office applications via Wine? With/without Crossover's product?
The installation process seemed to fail after what felt like an hour - but the whole suite of apps just worked after a reboot - no fiddling required.
Also - did you need to reboot your Linux host machine or perform some form of a "Wine layer reboot"?
I rebooted the whole PC - not sure if the Wine layer specifically would have been sufficient.
EDIT: in the sense that OSX or iOS programs could run on other platforms.
Also, Microsoft previously had a project called Islandwood.