wine users - Feb 2011 - quake3 running on mobile phone(arm processor) by wine

ogre(windows binary) running on ac100(arm linux)
http://www.youtube.com/watch?v=g2D6SZcrT_U

quake3(windows binary) running on ac100 (arm linux) 
http://www.youtube.com/watch?v=UAncqVtQyEQ

ogre(windows binary) running on n900(arm linux)
http://www.youtube.com/watch?v=yDqkvEyzFk0

quake3(windows binary) running on n900 (arm linux)
http://www.youtube.com/watch?v=erTkTsCO50o

implemented some dll(gles.dll,egl.dll) to run ogre and quake3.
I have develped wine(1.1.33) on arm since 2009. 

the result of dll-test that compare x86 with arm has come close to 99%

i bet that's through qemu, which qemu version do you use?

Andr? H. wrote:
> i bet that's through qemu, which qemu version do you use?


This binary is compiled by winegcc.
The source code is composed win32api.

> There is no need for emulation, because all source code is compiled 
> for ARM.
Really? Maybe I'm missing certain concepts about how executable files work,
but these apps you're running are x86-based exe files, right? So there has
to be some sort of emulation or conversion going on somewhere... unless these
exes actually never send any sort of x86 instructions to Wine and only rely on
libraries?

At least, the fact that Wine had to be coupled with QEmu for PPC Macs indicates
that this has to happen. If you have somehow found a way to make Wine work on
any processor architecture (or at the very least ARMs), that would suddenly make
Wine a whole lot more portable.

Ahh, okay then. I was confused because you were still running executable files
in Wine. Well done.

Well, it is not my project, so compliments should go to the author. I
just tried to explain how it works. :)

On Fri, Feb 11, 2011 at 5:16 PM, DaVince <wineforum-user at winehq.org>
wrote:
> Ahh, okay then. I was confused because you were still running executable
files in Wine. Well done.
>
>
>
>
>
>

Now i want to mention that i am (until now) the only Wine on ARM developer, as
my patches are upstream...