501
Subj : Re: converting coff libs to omf libs
To   : borland.public.cpp.borlandcpp
From : Bob Gonder <notbg@notmindspring.invalid>
Date : Tue Sep 16 2003 11:13 am

trevor Arsenault wrote:

>I created the lib using IMPLIB in Borland 5.02, then I added the lib to my
>project and set the path to find the lib, but 3 of 6 functions
>in my __declspec(dllexport)..ed class are still showing as unresolved
>externals. Could this be because the lib file does not contain the full
>definition? The file is half the size of the COFF lib...don't know the
>structure inside a lib file so I don't know if the size means anything.

You're supposed to be able to use TDUMP on your LIB to see what
functions are in there.
I don't know if TLIB will list an import library or not.
IMPDEF is supposed to make a DEF file (text) from the DLL that you can
read/edit and then IMPLIB the DEF to a LIB also.

So, that's how you can find out what's in there.  Now, about why....
You said these were VC++ functions, right? C++ names are normally
mangled, and AFAIK there is no standard mangling convention, so....
Borland is probably looking for a differently mangled name than what's
in the DLL/LIB.
I think declairing the functions extern "C" on both sides  whould fix
that.

.

0