Question

My company provides a third party with a DLL which provides them with API functions they can use to connect to our application. The DLL was written in VC9, and the API functions used VC’s default calling convention (__cdecl). The third party has built their application around this interface.

I have now been tasked with writing an updated version of the DLL. We want the DLL to have exactly the same interface as the old one so they can be used interchangeably. Unfortunately, our development environment is now CodeGear RAD Studio 2007, so I have to write the DLL using that.

The best solution would be to make both the old and new DLLs export their functions as __stdcall. The third-party application could then be re-linked to expect __stdcall functions and everyone would be happy. Unfortunately, for various reasons this is unlikely to happen.

Alternatively, I can declare the functions in my DLL as __cdecl. The third-party expects __cdecl functions so this would seem to be a good solution. Unfortunately CodeGear insists on appending an underscore (‘_’) to the name of __cdecl functions. This means that the third-party application would have to make conditionally call MyApiFunction(...) or _MyApiFunction(...), depending on which DLL they use.

So my question is, how can I export the API functions from my new DLL in such a way that they are __cdecl and are not prefixed with an underscore (‘_’)?

Answer 1

You should use .DEF file:

EXPORTS
    HTMLayoutClassNameA = HTMLayoutClassNameA
    HTMLayoutClassNameW = HTMLayoutClassNameW
    HTMLayoutClipboardCopy = HTMLayoutClipboardCopy
    ...

Here we have

externalname = internalname