Subj : Re: Video for Windows import library
To   : borland.public.cpp.borlandcpp
From : "Ed Mulroy [TeamB]" <ed@mulroyREMOVETHESECHARS.org>
Date : Thu Aug 07 2003 08:04 pm

The implib32.lib that Borland supplies covers many different DLL's.
Microsoft does it differently, having a separate import library for each of
many DLL's and their literature covering their DLL's often references
individual import libraries for each.  Before you decide to implib and use
that other library, check for if implib32.lib already supports it.  You can
see what it supports with a command like this one to create a list file
(*.LST) listing the contents of the import library:

  tlib /C  import32.LIB  ,  import32.LST

Because the compiler you are using, Borland C++ 5.02, was created in 1997 it
should not be a suprise that additional things have come out in the past 6
years.  Adding support for such additional things would be up to you.

If you end up with 2 or more system DLL's that you need to use which don't
have support in the import32.lib file then you could create your own import
library for them so that only one additional lib would be needed.  A
contrived example of doing that is:

impdef aaa.def  c:\winnt\system32\aaa.dll
impdef bbb.def  c:\winnt\system32\bbb.dll
impdef ccc.def  c:\winnt\system32\ccc.dll
implib -c  myimplib.LIB   aaa.def   bbb.def  ccc.def

Do not on your first attempt try to create a replacement for import32.lib
There are duplicate symbol issues and naming issues (courtesy of what
symbols are in those MS DLL's) which have to be resolved by manually editing
*.DEF files to get that to work.

..  Ed

> Tim Jackson wrote in message
> news:3f32b57b$1@newsgroups.borland.com...
> Is there a Borland version of the import library VFW32.LIB available
> for download anywhere? Alternatively is there a list of the DLL's
> used by IMPLIB to build it?
>
> I am using Borland C++ 5.02 to develop a video application under
> Windows 98, and find that in order to use entry points from VFW.H
> I need an import library to connect it to the Windows DLL(s), and I
> there is none supplied with the compiler.
>
> So far I've managed to make it work by hunting through
> windows\system and IMPLIBbing the relevant DLLs, but it seems
> every time I do something new I need to spend time figuring out
> where the entry points are.  It would be nice to have the whole lot
> in one place.

.