Board index » cppbuilder » Compatible DLL for Visual and Borland C++ projects

Compatible DLL for Visual and Borland C++ projects


2006-11-13 04:48:53 PM
cppbuilder31
Hi,
I have a DLL project for Visual C++ 6 and I would like to use
this DLL with borland program. So I passed it into IMPLIB tool to
have the corresponding .LIB file, but I always have a link error.
The only solution I found is to pass by the converting tool
given by Builder and to export the makefile. In this way, the
generated DLL is always compatible, but project integrity is hard
to keep safe :
For each modification, you must :
- export the makefile,
- test the compatibility with the other project.
Does anyone know how to have only one project (Visual or Builder)
and how keeping the resulting DLL compatible for Visual project ?
Is there project option to avoid ?
Thanks.
Franck
 
 

Re:Compatible DLL for Visual and Borland C++ projects

"Franck B" < XXXX@XXXXX.COM >wrote in message
Quote
Does anyone know how to have only one project (Visual or Builder)
and how keeping the resulting DLL compatible for Visual project ?
Using Visual C++ DLLs in a C++Builder Project
web.archive.org/web/20041204120939/http://www.bcbdev.com/articles/vcdll.htm
Visual C++ DLLs Part 2: C++ Classes
web.archive.org/web/20041204120939/http://www.bcbdev.com/articles/vcdll2.htm
Creating DLLs in BCB that can be used from Visual C++
web.archive.org/web/20041204120939/http://www.bcbdev.com/articles/bcbdll.htm
Gambit
 

Re:Compatible DLL for Visual and Borland C++ projects

did you try adding
#if defined __cplusplus
extern "C" {
#endif
__declspec(dllexport) type __stdcall my_function()
or something like that?
"Franck B" < XXXX@XXXXX.COM >ha scritto nel messaggio
Quote

Hi,

I have a DLL project for Visual C++ 6 and I would like to use
this DLL with borland program. So I passed it into IMPLIB tool to
have the corresponding .LIB file, but I always have a link error.
The only solution I found is to pass by the converting tool
given by Builder and to export the makefile. In this way, the
generated DLL is always compatible, but project integrity is hard
to keep safe :
For each modification, you must :
- export the makefile,
- test the compatibility with the other project.
Does anyone know how to have only one project (Visual or Builder)
and how keeping the resulting DLL compatible for Visual project ?
Is there project option to avoid ?

Thanks.

Franck
 

{smallsort}