DarkShadow44 wrote:I very much doubt it would work like this. You would need to emulate a whole kernel too, you need some sort of distro in which your wine can run, don't you? You can't just throw wine into an emulator without kernel.
Or you go the
Project Hangover route. But just know, either way, it's very hard.
Yes, the QEMU can use
user space mode to run X86 executable file on non X86 CPUs. You can see the
section 5.3 and get the message from the
QEMU web document.
I had seen the project of
Project Hangover from the GitHub. But the project is running a few simple
Win64 applications on
arm64 Linux and
Android, that is not my need. Meanwhile, I don't have no ability to modify the source code of Wine and Qemu, like the Project Hangover do.
Now, I have
two choices from the email message of the
QEMU developers:
(1)If the
Wine executable file was made by
static compilation, the normal Qemu can run it directly and it can run successfully.
(2)If the
Wine executable file was made by
dynamic compilation, I must set up a Qemu based
chroot on my host Linux distro and use chroot to get the related DLLS, data files and other things it requires.
So, I ask the function to compile Wine statically on the forum. I try the second function on my PC withe the MIPS architecture. The process is hard. This is what I have gained so far.
@
DarkShadow44, thanks again.