Subj : Re: Converting a VC++ DLL to BCW
To   : borland.public.cpp.borlandcpp
From : Ed Mulroy [TeamB]
Date : Tue Dec 28 2004 10:01 am

If the DLL exports any C++ items that are classes or
functions that accept arguments that are classes,
pointers to classes or references to classes then
you cannot use those items in the DLL.  Microsoft
uses a different memory layout in their classes, a
layout that is different from what Borland uses.

If you have the DLL then you should have a header file
that provides function prototypes for the items exported
by the DLL.  Therefore you already know the source
code names for the functions with their calling argument
list and calling conventions.

While the format used by Microsoft's tools in creating
a DLL has evolved with time the tools you are using are
from BC++ whose last edition was in early 1997.  They
may not find everything in that DLL.

Try this:

Give a command like the one below and then manually edit
the file containing the redirected output, inserting aliases for
the functions shown into a module definition file.  Afterwards
add the module definition file to the project.

tdump -m c:\windows\system\msvcr71.dll >x.txt

..  Ed

> Wilbur wrote in message
> news:41d154b4$1@newsgroups.borland.com...
>
> I have an 8KB VC++ DLL to convert to a Borland C++
> library. I've tried the recommended IMPDEF/IMPLIB
> conversion.  With IMPDEF I get only one symblo
> (which I edited as required).  With IMPLIB I get a 1KB
> library that does not work (externals can't be found by
> the linker).  Help!

.