Here is the correct def and .a files for VideoForWindows stuff, thanks to
Luke Dunstan who points me to way to fix it. I have tested it with my code,
it's working without problem so far. The missing header files vfw.h and one
other(I forgot the name), I copied them from Platform sdk. Also instead of
linking with libvfw32.a, you will need to link with the 3 .a files attached
with this mail.
could someone help me check this to the win32api
> ----- Original Message -----
> From: "Luke Dunstan" <coder_infidel@...>
> To: "psksvp" <psksvp@...>; <mingw-users@...>
> Sent: Friday, May 23, 2003 8:38 PM
> Subject: Re: [Mingw-users] vfw.h anyone still working with it??
> > ----- Original Message -----
> > From: "psksvp" <psksvp@...>
> > To: <mingw-users@...>
> > Sent: Friday, May 23, 2003 2:48 PM
> > Subject: [Mingw-users] vfw.h anyone still working with it??
> > > I have code that read and write avi file, trying to compile it, vfw.h
> > > missing, so I copy it from psdk. now it compiles and and links without
> > > problem, but when I try to run it, a MessageBox popup saying that
> > > "AVIFileAddRef" is missing from msvfw32.dll, so I check msvfw32.dll in
> > > system32 dir, there is no "AVIFileAddRef" in there. This is what
> > me,
> > > the code is compiled and linked with VC6 and BCC55 without the same
> > problem.
> > >
> > > Is there anyone using the API and have any success??
> > >
> > > psksvp
> > >
> > > PS I am using winXP and mingw32-gcc 3.2.3 and the lasted runtimes
> > The short answer is: use Google. I found:
> > http://sources.redhat.com/ml/cygwin/1999-11/msg00672.html
> > and
> > http://groups.yahoo.com/group/mingw32/message/3318
> > Basically, you need to create an import library for avifil32.dll (and
> > possibly avicap32.dll) and link with that as well as -lvfw32. As these
> > explain, the MS vfw32.lib contains imports for multiple DLLs, but AFAIK
> > MinGW import libraries do not support this directly. The easiest way for
> > to do this is probably by getting vfw32.def from the w32api source,
> > splitting it into 3 .def files and creating import libraries like:
> > dlltool -k --output-lib libavifil32.a --def avifil32.def
> > If you end up doing it yourself then you won't have to wait for a new
> > release of w32api and you can actually test the import libraries on your
> > code (which a MinGW developer cannot do, otherwise this would already
> > You could then submit a patch to be incorporated in w32api :-).
> > Luke
> > -------------------------------------------------------
> > This SF.net email is sponsored by: ObjectStore.
> > If flattening out C++ or Java code to make your application fit in a
> > relational database is painful, don't do it! Check out ObjectStore.
> > Now part of Progress Software. http://www.objectstore.net/sourceforge
> > _______________________________________________
> > MinGW-users mailing list
> > MinGW-users@...
> > You may change your MinGW Account Options or unsubscribe at:
> > https://lists.sourceforge.net/lists/listinfo/mingw-users