Linked by Thom Holwerda on Tue 17th Jul 2012 22:19 UTC, submitted by Nth_Man
Thread beginning with comment 527184
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
The thing is that while wine is a good solution for playing windows games on x86/x86_64 linux. It is not useful for other architectures.
As there are some rumours going around about Valve wanting to build some kind of linux based gaming device (console) they would profit from porting to linux instead of using wine. As wine does not work on other architectures, but when something is ported correctly it should be trivial to recompile for other architectures (arm anyone?).
but when something is ported correctly it should be trivial to recompile for other architectures (arm anyone?).
Unless it contains a significant amount of assembly code, which is still very common for the highly optimised code paths found in some game engine. Not counting, that when it comes to ARM, you need to select which core you are targeting.
The thing is that while wine is a good solution for playing windows games on x86/x86_64 linux. It is not useful for other architectures.
Yes, it is. wine is easily cross-installable if you have Debian Wheezy or newer:
dpkg --add-architecture i386
apt-get update
apt-get install wine:i386 wine-bin:i386 qemu-user-static
That's all you need to be able to use wine on *ANY* architecture you want. Unless your host CPU is not too slow, you won't notice any difference running wine on a native i386/x86_64 machine.
Adrian
Edited 2012-07-18 15:39 UTC





Member since:
2010-06-08
Lately Wine helps for that pretty good, so in most cases Windows isn't needed at all even for games.