Re: Intent to get Avisynth working with Wine/Winelib

2003-09-10 Thread Kevin Atkinson
On Wed, 10 Sep 2003, Dimitrie O. Paun wrote: > On September 10, 2003 11:44 pm, Kevin Atkinson wrote: > > For now lets focus on getting Avisynth working. > > That's the best thing to do: is the Avisynth binary > working under Wine ATM? I'm sorry, What is Wine ATM? I filed the bug report since it d

Re: Intent to get Avisynth working with Wine/Winelib

2003-09-10 Thread Dimitrie O. Paun
On September 10, 2003 11:44 pm, Kevin Atkinson wrote: > For now lets focus on getting Avisynth working. That's the best thing to do: is the Avisynth binary working under Wine ATM? -- Dimi.

Re: Intent to get Avisynth working with Wine/Winelib

2003-09-10 Thread Kevin Atkinson
On Wed, 10 Sep 2003, Dimitrie O. Paun wrote: > On September 10, 2003 07:16 pm, Kevin Atkinson wrote: > > > It MIGHT be possible to make my C interface a winlib by using the > > functions as it (ie in assembly) and just relinking the lib. Is this even > > remotely practical and will it help matter

Re: Intent to get Avisynth working with Wine/Winelib

2003-09-10 Thread Dimitrie O. Paun
On September 10, 2003 07:16 pm, Kevin Atkinson wrote: > It MIGHT be possible to make my C interface a winlib by using the > functions as it (ie in assembly) and just relinking the lib. Is this even > remotely practical and will it help matters at all? It should be practical, but I'm afraid it do

Re: Intent to get Avisynth working with Wine/Winelib

2003-09-10 Thread Kevin Atkinson
On Wed, 10 Sep 2003, Dimitrie O. Paun wrote: > On Wed, 10 Sep 2003, Kevin Atkinson wrote: > > > On 10 Sep 2003, Mike Hearn wrote: > > > > I will repeat what I just said: > > > > Since it normal interface is VC++ RECOMPILING it under > > Winelib is NOT really an option as that will mean that

Re: Intent to get Avisynth working with Wine/Winelib

2003-09-10 Thread Kevin Atkinson
On Thu, 11 Sep 2003, Ove Kaaven wrote: > On Thu, 2003-09-11 at 00:29, Kevin Atkinson wrote: > > I will repeat what I just said: > > > > Since it normal interface is VC++ RECOMPILING it under > > Winelib is NOT really an option as that will mean that existing plugins > > for Avisynth will n

Re: Intent to get Avisynth working with Wine/Winelib

2003-09-10 Thread Ove Kaaven
On Thu, 2003-09-11 at 00:29, Kevin Atkinson wrote: > I will repeat what I just said: > > Since it normal interface is VC++ RECOMPILING it under > Winelib is NOT really an option as that will mean that existing plugins > for Avisynth will no longer work without a recompile. But that's also

Re: Intent to get Avisynth working with Wine/Winelib

2003-09-10 Thread Dimitrie O. Paun
On Wed, 10 Sep 2003, Kevin Atkinson wrote: > On 10 Sep 2003, Mike Hearn wrote: > > I will repeat what I just said: > > Since it normal interface is VC++ RECOMPILING it under > Winelib is NOT really an option as that will mean that existing plugins > for Avisynth will no longer work withou

Re: Intent to get Avisynth working with Wine/Winelib

2003-09-10 Thread Kevin Atkinson
On 10 Sep 2003, Mike Hearn wrote: > a rOn Wed, 2003-09-10 at 22:54, Kevin Atkinson wrote: > > What is this? > > > > Avisynth needs VC++. My API needs VC++ as it acts as the bridge and must > > make VC++ calls to avisynth. Everything can be gcc. And in fact I have > > successfully cross compi