How can i link a borland C++4.5 32 bits dll and object file
made with masm 6.11 in a Microsoft Visual C++ 4.2 project without getting unresolved link errors in object file? The problem is that Microsoft doesn't support good implib.exe programms which work with VC++4.2 or 5.0. So how can I do it anyway?
In Borland C++ 4.5 was the 32 bits dll made with declaration like this:
int _stdcall _export Name1(HWND hWnd);
and function declaration in the same Borland C++ 4.5
int _stdcall _export Name1(HWND hWnd)
// code who also use another 32 bit dll (also orginal borland)
The code in MASM 6.11calls Name1 like:
Name1 proto stdcall HWND:WORD
Hwnd1 word 0
After compiling in MASM6.11 I have a object file which should be
linked in MSVC++4.2 or 5.0.
Now I get: filename.obj error LNK2001 a unresolved external symbol _Name1@2
I make my lib file with def headers like this:
library filename1.dll //(borland dll)
description 'export function'
(MS-dos prompt, using the lib.exe of MSVC++4.2 : lib /def:filename.def /machine:IX86)
(This normally works correct for builded Delphi 2.0/3.0 DLL's)