I was redirected to wine-devel. Attached is the .inf file if it would
help.
--
http://kevin.atkinson.dhs.org
-- Forwarded message --
Date: Sat, 27 Dec 2003 14:50:48 -0500 (EST)
From: Kevin Atkinson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Installing from a
On Fri, 26 Dec 2003, Dmitry Timoshkov wrote:
> "Kevin Atkinson" <[EMAIL PROTECTED]> wrote:
>
> > If the names are not decorated in that fashion mingw has a problem linking
> > with it. When linked the linker is looking for the names with the
> >
On Fri, 26 Dec 2003, Dmitry Timoshkov wrote:
> "Kevin Atkinson" <[EMAIL PROTECTED]> wrote:
>
> > That is a heck of a lot of work to link with a DLL that is not compiled
> > with an exports table.
>
> I don't understand you. If a DLL exports somethi
On Thu, 25 Dec 2003, Dmitry Timoshkov wrote:
> "Boaz Harrosh" <[EMAIL PROTECTED]> wrote:
>
> > I did, I have tried both your suggestions.
> >
> > What ever you do. any thing after the @ sign gets truncated in the
> > import process and will not
> > Reach the Import table.
> >
> > Note that in
On Wed, 24 Dec 2003, Dmitry Timoshkov wrote:
> "Kevin Atkinson" <[EMAIL PROTECTED]> wrote:
>
> > So are you saying that it is not possible to fix winbuild to deal with DLL
> > witch only use __declspec(dllexport) to export their functions?
>
> How wou
On Wed, 24 Dec 2003, Dmitry Timoshkov wrote:
> "Kevin Atkinson" <[EMAIL PROTECTED]> wrote:
>
> > > Well yes they are decorated. This is the way the VC made them. I guess
> > > they are not Decorated only if you use a .DEF file. If you export them
&
On Wed, 24 Dec 2003, Boaz Harrosh wrote:
> Well yes they are decorated. This is the way the VC made them. I guess
> they are not Decorated only if you use a .DEF file. If you export them
> with __declspec(dllexport) they are exported decorated.
You are correct. If I use a .def file WITH the @
On Mon, 22 Dec 2003, Kevin Atkinson wrote:
> On Mon, 22 Dec 2003, Boaz Harrosh wrote:
>
> > I have stdcall working fine here.
> >
> > There is something wrong with your DLL the fact that "pexports" dumped
> > "_" before symbol names is a c
On Mon, 22 Dec 2003, Boaz Harrosh wrote:
> I have stdcall working fine here.
>
> There is something wrong with your DLL the fact that "pexports" dumped
> "_" before symbol names is a clue to those functions been exported as
> cdecl. In stdcall (or PASCAL) no under-scored is perpended. (and yo
Oops. Sorry that I left the subject off.
On Sun, 21 Dec 2003, Kevin Atkinson wrote:
>
> I am having a problem compiling a simple winelib program which relies on
> a dll which uses the stdcall calling convention. I used pexports on the
> dll avisynth_c.dll to created the s
I am having a problem compiling a simple winelib program which relies on
a dll which uses the stdcall calling convention. I used pexports on the
dll avisynth_c.dll to created the spec and then edited the file to removed
the leading underscore in the names (without that it would not link).
Tha
It seams that I wasn't using the winlib application at all. Instead there
was a left over exe that the launch script was finding and using
No that I tried to rebuilt it I can't get it working. I am getting:
wine: Unhanded exception (thread 0009), starting debugger...
err:seh:start_debugger
On Sun, 14 Sep 2003, Dimitrie O. Paun wrote:
> On September 13, 2003 08:32 pm, Kevin Atkinson wrote:
> > > > Furthermore it is still using windows I/O.
> > >
> > > Hmm, can you post the Makefile you used to build the thing?
> >
> > Attached is to file
On Sat, 13 Sep 2003, Dimitrie O. Paun wrote:
> On September 13, 2003 04:03 am, Kevin Atkinson wrote:
>
> > OK I figured out how to get it to compile. I manually created
> > libavisynth_c.def, it is attached. I know that wasn't the best thing to
> > do but it w
On Fri, 12 Sep 2003, Kevin Atkinson wrote:
> Here is what I got:
> avs2yuv4mpeg.cpp - the main program
> avisynth_c.h - header for DLL I need to link with
> avisynth_c.lib - lib "" "
>
> And I want to compile this into an executable avs2
I am having a hell of a time getting a simple program to link with a
windows dll. I am really sorry for the newbie question but I can't seam
to find an answer anywhere and the mailing list archive is not
searchable.
Here is what I got:
avs2yuv4mpeg.cpp - the main program
avisynth_c.h -
On Thu, 11 Sep 2003, Dan Kegel wrote:
> Kevin wrote:
> > BTW: You can find my C API at http://kevin.atkinson.dhs.org/avisynth_c/.
> > Avisynth: http://www.avisynth.org/. And a dead simple program as the
> > test case for the bug http://bugs.winehq.org/show_bug.cgi?id=1707 .
>
> That test case i
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 f
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 pr
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
On 11 Sep 2003, Mike Hearn wrote:
> On Wed, 2003-09-10 at 23:36, Kevin Atkinson wrote:
> > Can a linux application link with a winlib shared library.
>
> Nope. Not yet, anyway.
>
> > > -- run avisynth in a separate process, and devise some sort of
> > &
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 plugi
On Wed, 10 Sep 2003, Dimitrie O. Paun wrote:
> On Wed, 10 Sep 2003, Kevin Atkinson wrote:
>
> > > This is not currently possible, sorry. How big is this interface to
> > > avisynth? The only option ATM is to have it out-of-process, so we'll
> > > need to co
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 h
BTW: You can find my C API at http://kevin.atkinson.dhs.org/avisynth_c/.
Avisynth: http://www.avisynth.org/. And a dead simple program as the
test case for the bug http://bugs.winehq.org/show_bug.cgi?id=1707 .
--
http://kevin.atkinson.dhs.org
On Wed, 10 Sep 2003, Dimitrie O. Paun wrote:
> On Wed, 10 Sep 2003, Kevin Atkinson wrote:
>
> > My intent is to get Avisynth working under Linux with the help of
> > Wine/Winelib. Since it normal interface is VC++ recompiling it under
> > Winelib is not really an optio
Hi,
I am the developer of the C interface for Avisynth. Avisynth is a
very popular Open Source tool for for video post-production for Win32.
More information can be found at http://www.avisynth.org/.
My intent is to get Avisynth working under Linux with the help of
Wine/Winelib. Since it no
27 matches
Mail list logo
