🚀 go-pugleaf

Hi Jonathan,

> I have a CodeWarrior .DLL project on Windows that I am trying to
> exporting some C functions from.  The only problem is that they are
> __stdcall functions, not __cdeclspec functions.  What is the protocol
> for doing this?  I understand that I need to create an .exp or .def
> file containing them, but I do not see the format of this documented
> anywhere.

Check Targeting Windows under the "Creating Win32/x86 Dynamic Link
Libraries" / "Function and Variable Names" / "Exporting names" section, or
the "Module definitions file format" section.  I admit the hierarchy is kind
of weird, but all the details are there.

> If a function has say the following prototype:
>
> short __stdcall foo(short x);
>
> What is the proper syntax for exporting this from a CodeWarrior .DLL?
> And are there any examples out there that can show me how it is done?

You don't need a .def/.exp file at all (these are legacy methods).  Instead,
simply add "__declspec(dllexport)" to the declaration:

__declspec(dllexport) short __stdcall foo(short x);

And the linker will automatically export it.

In a client of the DLL you need __declspec(dllimport) instead.  You can
create a project from stationery (Win32 DLL) to see how to set up headers to
declare the function the right way for the implementation and the client.

If you really need to use a .def file, the easiest method is to specify:

EXPORTS
foo

and the linker should export the symbol named foo, no matter what its
calling convention is.

In the event you have multiple symbols with this root name, or the linker
can't find it, you'll get an error, and will have to use the actual symbol
name, which for a C function is probably "_foo@4", but for C++ it's a lot
hairier.  You can disassemble the file defining foo to see what the symbol
name is.  (Anyway, just use the __declspec -- it's there to avoid all this
crufty .def file nonsense).

-- Ed