Re: [Qemu-devel] Qemu: darwine flavour or bellard flavour?; darwine-qemu-fast?; darwine-wine-ppc+darwine-qemu-x86?

[Lionel Ulmer <lionel.ulmer@free.fr>]

> > http://www.winehq.com/site/docs/wine-faq/index#INTEGRATE-AN-X86-EMULATOR
> 
> You should add an automatic stub code generator which generates code to 
> swap the arguments for all wine entry points.

Which would work (maybe) for Win16 applications or 'simple' Win32 ones, but
as soon as you start to use COM, you need to take great care as there is
currently no way to know which are all the 'exported' functions (as they are
stored in VTables).

Moreover, in the current Wine code, there is absolutely no difference
between some Win32 code calling a Wine function or a Wine DLL calling a
function in another DLL. So there would need to be a way to differentiate
both (and it's the same issue for COM objects, as they can be invoked either
from Win32 or from Wine code).

Lastly, there is the issue of all the 'opaque' data types - data types for
which the format is known only once some processing has been done in the
called function (for example, a bitmap, a texture or some vertex buffer).

          Lionel

-- 
		 Lionel Ulmer - http://www.bbrox.org/