wine users - May 2011 - Is it possible to port (part of) WINE to iOS?

Since Apple's Mac X and iOS share the same kernel -- Darwin. And WINE has
port for Mac X.

Is it possible to port (part of) WINE to iOS? For example,
"winbase.h", etc.

The purpose for porting WINE to iOS is to provide source code level
compatibility for exist Win32 application.

Ahso,
First of all, I'm not a Mac freak, Linux in my main OS. Second, I never said
that open source was illegal. I said that JAILBREAKING is NO LONGER illegal, to
prevent people from thinking that I was posting about illegal things, especially
given that that is against forum rules. Third, whether Darwine is obsolete or
not is irrelevant - I was merely referring to it to show that it is possible to
run WINE on a processor emulator. Fourth, don't bite the hand that feeds
you.

Everyone,
Anyways, I hope I have shown how it is possible to develop a WINE app for iOS
running on the A4 without the AppStore, and without having to get a signature
from Apple, bypassing any of Apple's restrictions, which, to remind again,
isn't illegal anymore - details in my previous post and the links therein.

Cheers,
Jake

I said that you can place wine ON TOP OF a processor emulator, not that it is
one.
Let's break this down. A processor runs a program called a kernel. That is
the only program the processor runs directly, unless you have a rootkit, which
is usually pretty bad.
All your other programs are ran by the kernel, which passes code onto the
processor.
Therefore the kernel and the pieces of programs that get passed onto the
processor must be in terms that the processor can directly execute.
WINE is a kernel ran by another kernel. It passes code from the Windows
applications it is running onto the host kernel to be passed to the processor.
There is no translation of processor-level instructions being translated from
one processor's instruction set to another processor's instruction set
anywhere in there.
Therefore, in order for WINE to run programs compiled for (in terms of) an x86
processor, WINE must have an x86 processor.
That processor can be a physical x86 processor, or it can be an emulated one.
I said that you can place wine ON TOP OF a processor emulator, not that it is
one. A WINE app would have to come with it's own x86 processor emulator
packaged as a part of the app. To make such an emulator would be an endeavor
separate from the WINE project. That doesn't mean we'll have to hate
that dev team or anything; it would just be a separate project.
Hope that clears it up. I didn't mean to make any confusion.
And by the way, Ahso, I wrote this post on my iPhone. Come on, you got to have
some humor.
Cheers,
Jake

SpawnHappyJake wrote:
> I said that you can place wine ON TOP OF a processor emulator, not that it
is one.
This is what the Darwine project tried to do for Power PC based MacIntosh
computers.  I was horribly slow.
The good thing is that Wine can still be built on PowerPC based computers and is
in the process of being configured to run on ARM based processing devices.  The
main holdup after that is an ARM <-> x86 emulator that will not bring
everything to a crawl.

SpawnHappyJake wrote:
> 
> WINE is a kernel ran by another kernel.
> 
No, WINE is NOT a kernel.  It is a user-space program the acts as an interface
providing Windows Application Programming calls to and from Windows based
programs and translates them into Linux/UNIX programming calls.  Thus if a
program calls a DirectX 10 function, the call and its data are translated into
an equivalent Linux/UNIX OpenGL call.  DirectX 10, in and of itself does not
exist The reason I state that WINE is not a kernel is because it cannot run any
Windows hardware/software drivers.  If this were possible, many of the
complaints about WINE would not exist.

Wow! Thanks a lot James McKenzie! I have a much better understanding of Wine
now, as well as what it takes to have a true kernel.

Ryan Woodsmal, l didn't forget about you. Wikipedia has great stuff on
explaining what a kernel is. Here's
one:http://en.wikipedia.org/wiki/Kernel_%28computing%29. Wikipedia says that the
supervisory program is usually called the kernel, so here's another:
http://en.wikipedia.org/wiki/Supervisory_program. Maybe we can talk about what a
kernel is later, I got to get to bed. Maybe a Pastebin or something.

Anyways, are there any smart phones that use the x86 instruction set?

I know that running Crysis on Wine on a processor emulator on the iOS kernel on
the iPhone hardware is NOT a good idea. That said, running a Windows program in
Wine on a processor emulator on the iOS kernel on the iPhone hardware is a much
better idea than using DOSBox for iOS to run a Windows program in Windows 98 in
DOSBox on DOSBox's emulated processor on the iOS kernel on the iPhone/ iPad
hardware.
Ahso said he just wanted to run a Windows command line program. Something
microscopic like that should be able to run on Wine on a processor emulator on
the iOS kernel on the iPhone/ iPad/ iPod Touch hardware, right? I guess it
depends on the command line program, but I would hope it's small. But James
McKenzie is right that it would be ASTRONOMICALLY better to port the command
line program to be a native iOS app, but that may or may not happen. Not like
Wine for iOS would happen.

But if anybody can find a smartphone with a physical processor that uses the x86
instruction set, that might be able to run Windows programs in a port of Wine
well.

Cheers,
Jake