Re: Wine as shared library patch

2004-03-09 Thread Mike Hearn
On Tue, 09 Mar 2004 09:51:40 -0500, Miguel de Icaza wrote: > Our issue is that we would need to create yet another package with a > different dependency chain. If you ship this you make our live a lot > simpler. > > But we will ship it ourselves if we absolutely have to. I'm not sure I understan

Re: Wine as shared library patch

2004-03-09 Thread Boaz Harrosh
Miguel de Icaza wrote: Hello, Yep Now, this might not be as helpful to others as you might thinkg, unless they dlopen/dlsym every symbol they want to import (this is what we do with Mono: every symbol we need has to be explicitly invoked). Yes that. But what if I dlopen From

Re: Wine as shared library patch

2004-03-09 Thread Miguel de Icaza
Hello, > I strongly disagree! > > I'm not sure what this patch can do. But if it lets you Inject into wine > mid run from any Linux application or Library than it is tremendous. > MPlayer can use it, a unixODBC to windowsODBC can use it, web-browser > plug-ins can use it. The intention is to

Re: Wine as shared library patch

2004-03-09 Thread Miguel de Icaza
Hello, > > Could we get this in the official Wine distribution? Peter's patch > > includes the Makefile and configure magic as well (the rest could be > > dropped). > > I would really prefer for you to ship it yourself. This is not a > general solution, and we don't want other projects to start

Re: Wine as shared library patch

2004-03-09 Thread Boaz Harrosh
Mike Hearn wrote: For the record there are still a ton of unresolved questions that Mono is just choosing to ignore here (because they can). For instance, multithreading won't always work correctly, but as S.W.F is not thread safe this doesn't seem to matter too much. I think stuff like exceptio

Re: Wine as shared library patch

2004-03-09 Thread Mike Hearn
On Tue, 09 Mar 2004 12:27:17 +0200, Boaz Harrosh wrote: > I strongly disagree! > > I'm not sure what this patch can do. But if it lets you Inject into wine > mid run from any Linux application or Library than it is tremendous. > MPlayer can use it, a unixODBC to windowsODBC can use it, web-brows

Re: Wine as shared library patch

2004-03-09 Thread Boaz Harrosh
Alexandre Julliard wrote: Miguel de Icaza <[EMAIL PROTECTED]> writes: Could we get this in the official Wine distribution? Peter's patch includes the Makefile and configure magic as well (the rest could be dropped). I would really prefer for you to ship it yourself. This is not a general

Re: Wine as shared library patch

2004-03-08 Thread Alexandre Julliard
Miguel de Icaza <[EMAIL PROTECTED]> writes: > Could we get this in the official Wine distribution? Peter's patch > includes the Makefile and configure magic as well (the rest could be > dropped). I would really prefer for you to ship it yourself. This is not a general solution, and we don't want

Re: Wine as shared library patch

2004-03-08 Thread Miguel de Icaza
Hello, > Miguel de Icaza <[EMAIL PROTECTED]> writes: > > > 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. > > Something along these lines should do the trick: I tested something li

Re: Wine as shared library patch

2004-03-08 Thread Alexandre Julliard
Miguel de Icaza <[EMAIL PROTECTED]> writes: > 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. Something along these lines should do the trick: #include #include #include #include #i

Re: Wine as shared library patch

2004-03-08 Thread 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 dictate

Re: Wine as shared library patch

2004-03-08 Thread Alexandre Julliard
"Peter Dennis Bartok" <[EMAIL PROTECTED]> writes: > 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

Re: Wine as shared library patch

2004-03-08 Thread Peter Dennis Bartok
: "Peter Dennis Bartok" <[EMAIL PROTECTED]>; "Robert Shearman" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Date: 07 March, 2004 17:37 Subject: Re: Wine as shared library patch >Miguel de Icaza <[EMAIL PROTECTED]> writes: > >> Well, the issue i

Re: Wine as shared library patch

2004-03-08 Thread Miguel de Icaza
Hello, > >> Perhaps this could be changed to a static variable in process.c > > Wouldn't that make it rather hard to be set from outside process.c? I > > need to set it from wine-sharedlib.exe.so > > It seems to me that you could simply do a longjmp() out of your > WinMain, and then you wouldn't

Re: Wine as shared library patch

2004-03-08 Thread Miguel de Icaza
Hey, > > Well, the issue is that our WinMain is never called, and we would > > rather not depend on this in our patch, but instead get the small > > global that says `Hey Wine, just return'. > > The global variable thing is ugly; we could export a different entry > point instead, but I'm not sure

RE: Wine as shared library patch

2004-03-07 Thread Robert Shearman
Alexandre Julliard wrote: > Miguel de Icaza <[EMAIL PROTECTED]> writes: > > > Well, the issue is that our WinMain is never called, and we would > > rather not depend on this in our patch, but instead get the small > > global that says `Hey Wine, just return'. > > The global variable thing is ugly;

Re: Wine as shared library patch

2004-03-07 Thread Alexandre Julliard
Miguel de Icaza <[EMAIL PROTECTED]> writes: > Well, the issue is that our WinMain is never called, and we would > rather not depend on this in our patch, but instead get the small > global that says `Hey Wine, just return'. The global variable thing is ugly; we could export a different entry poin

Re: Wine as shared library patch

2004-03-04 Thread Alexandre Julliard
Peter Dennis Bartok <[EMAIL PROTECTED]> writes: >> Perhaps this could be changed to a static variable in process.c > Wouldn't that make it rather hard to be set from outside process.c? I > need to set it from wine-sharedlib.exe.so It seems to me that you could simply do a longjmp() out of your Wi

Re: Wine as shared library patch

2004-03-04 Thread Peter Dennis Bartok
Perhaps this could be changed to a static variable in process.c Wouldn't that make it rather hard to be set from outside process.c? I need to set it from wine-sharedlib.exe.so If you can resolve these issues then we can have a single Wine for Win32 and S.W.F! Well, you basically saw the hole hi

RE: Wine as shared library patch

2004-03-04 Thread Miguel de Icaza
Hello! > If you can resolve these issues then we can have a single Wine for Win32 and > S.W.F! We are running some SWF applications now with Mono and this patch; And we are fairly happy, since its a small patch to maintain this time. Of course, it would be best to make it part of Wine, so the u

RE: Wine as shared library patch

2004-03-04 Thread Robert Shearman
Peter Dennis Bartok wrote: > This patch allows to use Wine as a shared library. It will allow the > Mono project to use Wine as the backend for it's System.Windows.Forms > implementation. It looks as though Alexandre has done a good job with kernel32 and ntdll since the last time using Wine with M