Web lists-archives.com

Re: [Mingw-users] Problems creating linkable file from MSVC .lib

Chris <chricro@...> writes:

> I've been working more on trying to get this going. I tried adding
> non-annotated aliases to the def file myself both ways, 
>  ...
> and in both cases it links but has the same entry point error.
> I also looked at the vcand32.dll file in MS's Dependency Walker and it
> shows all the exported functions without  <at> XX annotations. Does this
> indicate that for the DLL expected calling convention is __cdecl instead
> of __stdcall or is it not conclusive?

It is not conclusive, as previously described mechanisms exist for
choosing whether the names are decorated or not. For example, if you
look at a Windows DLL such as kernel32.dll in Dependency Walker, you
will not see decorated names, but kernel32.dll exports __stdcall
functions. By the way, are you able to call functions that do not
take any arguments without the runtime errors? I believe that that 
would indicate that it is a calling convention mismatch.

Another quick test would be trying to call the functions from
Visual Basic (not .NET; create a macro in Ms Word or Excel). VB
can call stdcall functions in a DLL, but cdecl functions will cause
a run time error:
Run-time Error '49':
Bad DLL Calling Convention 

John Brown.

Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
MinGW-users mailing list

This list observes the Etiquette found at 
We ask that you be polite and do the same.  Disregard for the list etiquette may cause your account to be moderated.

You may change your MinGW Account Options or unsubscribe at:
Also: mailto:mingw-users-request@xxxxxxxxxxxxxxxxxxxxx?subject=unsubscribe