Re: unresolved external symbol/using an external dll

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Michael J. Salamone [eMVP] (mikesa#at#entrek#dot#com)
Date: 05/01/04 

Date: Fri, 30 Apr 2004 19:09:15 -0700

You're right - I didn't read closely enough.

So, it's one of the two - the calling convention or the name mangling.
Dumpbin will shed light.

If you see _ and something like @8 at the end of a name, it's stdcall,
otherwise cdecl. If it's name mangling, you'll know it when you see it -
lot's of extra characters in front and in back of the name. And, it just
might be both. You'll have to adjust the declarations in your header file
appropriately. 

-- 
Michael Salamone [eMVP]
Entrek Software, Inc.
www.entrek.com
"Carl Daniel [VC++ MVP]" <cpdaniel_remove_this_and_nospam@mvps.org.nospam>
wrote in message news:%23jmzeexLEHA.3872@TK2MSFTNGP12.phx.gbl...
> Michael J. Salamone [eMVP] wrote:
> > Actually Windows CE only has cdecl calling convention.
>
> I got the impression that the OP is using code to read a CE database
outside
> WinCE.  The presence or absense of extern "C" may very well be the problem
> as well - good point.
>
> -cd
>
>
>

Relevant Pages

  • Re: unresolved external symbol/using an external dll
    ... it's one of the two - the calling convention or the name mangling. ... Michael Salamone [eMVP] ...
    (microsoft.public.windowsce.app.development)
  • Re: unresolved external symbol/using an external dll
    ... it's one of the two - the calling convention or the name mangling. ... Michael Salamone [eMVP] ...
    (comp.lang.cpp)
  • Re: calling from c# into a dll
    ... I remember the mangling issue from when I had to call C ... but the C# docs are silent on the issue. ... What do I do when I want to export a C++ class in a dll to a C# program? ... > sure the calling convention is cdecl ]). ...
    (microsoft.public.dotnet.languages.csharp)