RE: [Mingw-users] [mingw - StupidTechiQuestions] VB 6.0 and MinGWcustom DLL

[Anand, V. R <vai...@bo...>]

Hello "paulmingw":

Benny Riefenstahl's response to this question is correct on all counts.
You should be using single quotes in the C/C++ code and the reason the
VB form is unable to find the entry point in the DLL is almost certainly
because the exported symbol name has been mangled. When I used gcc to
compile the C code and dllwrap to create the DLL, the exported symbol
name remains 'cvtup'. You can verify this by looking at the output
cvtup.def created by dllwrap or use some symbol extraction utility like
objdump. For the same code, when I compiled it with g++ and used dllwrap
to create the DLL, the exported symbol name looked like '_Z5cvtupPc';
you should check your cvtup.def. You can then use the Alias keyword in
the Declare statement in the VB code to tell it the real symbol name to
look for. For example:

 Private Declare Function cvtup Lib "C:\Documents and Settings\Admin\My
Documents\Com-MinGW\VbStringConverter\cvtup.dll" _
    Alias "_Z5cvtupPc" (ByRef Bstr As Byte) As Long

That should take care of the problem.

Regards,
V.R.Anand


-----Original Message-----
From: pau...@wi... [mailto:pau...@wi...]=20
Sent: Monday, December 20, 2004 3:20 AM
To: min...@li...
Subject: RE: [Mingw-users] [mingw - StupidTechiQuestions] VB 6.0 and
MinGWcustom DLL


Hi V.R.Anand and Reg:
  I tried your example V.R. Anand and I am having some proplems with it.
Fist I will state my code, and from there explain the reasons for my
changes.
...