Wine as shared library patch

[Miguel de Icaza]

hello,m

> > Having Wine set up the TEB and stack environment and actually call our
> > WinMain and us then trying to 'undo' that in WinMain creates potential for
> > future breakage of our library, in case you change something related to
> > the TEB & stack.
> 
> The TEB & stack layout are dictated by binary compatibility, and are
> much less likely to change than the Wine init code. It's not clear to
> me at all that this global variable hack is the right interface for a
> proper shared library implementation, and I'm not going to commit to
> supporting that interface in the future.  OTOH WinMain and the TEB
> layout are not going to change, so you should build on top of that.

It still makes the code too hard for us to maintain.

Our patch is simple, and we lack the experience to work on Wine, TEB and
what not.    We just do not have the time to learn everything there is
to Wine. 

For now, we will ship a different Wine RPM, and use a different prefix
to avoid conflicting or something like that.  

Miguel.