🚀 go-pugleaf

In <C0wsLI.Dwy@fig.citib.com> ghica@fig.citib.com (Renato Ghica) writes:

>I have a third party DLL (pc-dce from Gradient), which they say
>has been linked under microsoft c++ API. This library does not
>work (undefined symbols when linking) in a BC++ 3.1 environment.
>The third party vendor is stumped. They have tried and can't get it
>to work under BC.

>Has anyone gotten a MSC /API dll to link in a BC++ 3.1 application?

    First, I would like to apologize for being so late in responding to
this question.  We have been extremely busy finishing up the next
release of our PC-DCE product and were unable to follow this 
thread.

    Although this question has led to a very interesting discussion
concerning C++ incompatibilities between the MSC and Borland 
compilers with regard to DLLs, it misrepresents the problem.

    The problem is not with linking to DLLs, but with static libraries.
Our product consists of a very small static library and a large DLL.  The
static library is used to transparently hide some data sharing that takes
place between the user's application and our DLL.  The linker is complaining
about some symbols in the static library.  

    This static library is built using the Microsoft LIB utility that 
is included in the C 7.00 toolkit.  The object modules are also compiled
with the C 7.00 compiler.  Neither our static library nor our DLL is 
built using C++, it is straight C code.  As far as our DLL is concerned, 
we do use the _pascal keyword on our entry points wherever possible. 

    We are investigating various options to remove this problem.  One is
to ship Borland versions of the static library.  Of course, this 
conversation would then take place again whenever someone wants to use
a compiler other than Borland or Microsoft.  Another alternative would
be to remove the static library altogether and expose a lot of messy
details to the application developer.

    So, I guess we should rewrite the question as "Has anyone gotten a
MSC static library to link with a BC++ 3.1 application?"  

    We do want to solve this problem so that we can provide Borland 
toolkit users with the same level of support that we currently provide 
with the Microsoft toolkit.  

    Any suggestions or comments regarding our products are welcome.

----------------------------------------------------------------------
Kevin Farrington			(kevin@gradient.com)
PC-DCE Project Leader
Gradient Technologies, Inc.
-- 
Kevin Farrington			(kevin@gradient.com)
PC-DCE Project Leader
Gradient Technologies, Inc.