I want to compile wine to another architecture,such as ARM,MIPS,PPC. But How to do this ? Thank you in advance.
yaocong wrote:> I want to compile wine to another architecture,such as ARM,MIPS,PPC. But How to do this ?It's not recommended to do so: http://wiki.winehq.org/ARM Also what exactly are you trying to archive with it? Wine does not emulate CPU, this means that on not x86 platform you won't be able to run native windows applications.
I want to run x86 binaries in QEMU and redirect the win32api to the wine as a BACKEND on ARM/MIPS platform. The major modification for the Wine is located at : 1,WINEGCC 2,WINEBUILD 3,NTDLL Currently I am using a mips64 machine to do the compiling ,so compile job is smooth,but the modification must be done before the compiling process can successfully finished. Any good suggestion will be appreciated! And I will contribute the the total project to wine.Thank you.
By the way,the Wine runs natively on the ARM/MIPS ,not in the Qemu sandbox.
You probably did not note the trace on that screenshot (http://dawncrow.de/arm4.png) and that running putty had resulted from cross compiling by means of winelib. Andr? launched putty binary in qemu emulating an arm machine so that it was convenient for him to take a screenshot, if I got his explanations right. Code: dawncrow at qemu-test:~$ uname -m armv5tejl dawncrow at qemu-test:~$ Please make it clear: 1. Just what OS architecture do you want to run in qemu? 2. Just what architecture do you want to run wine compiled for? 3. what does run what? Is it an ARM version of OS, which runs an ARM version of wine which, in turn, runs ARM version of qemu which, in turn, runs x86 binaries, or anything else?
Sorry I have not make the sense clear! I want to run wine on MIPS architecture in Linux,not by Qemu. and the Qemu is also running on MIPS and just emulates the x86 instructions to MIPS. This is the basic scenario:the two kits are running independently on MIPS. What I want to do is to run x86 instructions in qemu and the winapi calls will be directed to wine .So the program flow is like this: win32 applications(X86) -> qemu (translate)-> wine (win32 api)
Darwine is almost just what you need, excepting the fact that it is meant to run on PPC instead of MIPS and very far from being complete. The most easy way of running x86 binaries on mips is qemu, any other ways will require many months of hard work.