Re: porting troubles
Quoting Michael Schmitz <email@example.com>:
> > > Wine so the code may be unportable. There's still enough in the way
> > > windowmanager-Corel interaction to make you cry).
> > Using wine as a porting library is not x86 specific. Companies could
> use it to
> > quickly port to Linux, testing the response from the community and
> then doing a
> > real port. I'm sure Corel could port Wordperfect to PPC/Linux just by
> > "make". (They also used an abstraction layer to port Wordperfect to
> Using Wine _is_ x86 specific in the sense that Wine emulates enough of
> Windows low level API to let x86 code including DLLs run on Linux. To my
> knowledge, there is no port of Wine to another architecture. You cpould
> argue Wine can be run under some x86 emulator - does making Windows apps
> run on VirtualPC constitute a Linux port?
Yes, using wine -as an emulator- is x86 specific. Using wine as what it's
intended in the first place, a library, is not x86 specific. As long as you are
only using libraries supplied by wine (to replace the windows ones) and
recompile the other libraries your program is using (like, say, a gui .dll), you
can run these programs on anything wine compiles on.
Of course, you'll still have the "normal" porting problems, like byte-swapping,
assembly and co.
But, hell yes, it is a *real* port. It runs natively. It's like when you
recompile quake on PPC, you're not emulating DOS.
> Anyway, the point is moot (yet).
Wine is well, kinda slow anyways. And it looks like windows.