.def files C/C++ DLLs

by

I find the use of both __declspec(dllexport) and the .def file together to be useful in creating portable DLLs, i.e. DLLs that can be called from code compiled with a different compiler or with different compiler settings.

Just putting __declspec(dllexport) on your function declarations will cause those functions to be “exported” by your DLL (at least on Windows) so that they can be called from outside the DLL.

However, adding to the build a .def file that lists all of your exported functions lets you stop Microsoft compilers (for example) from adding a leading underscore and trailing parameter-width information to the exported function name (at least when combined with the __stdcall directive, also useful for portability). E.g. the function declaration

void foo(int i);

could end up being exported as “_foo@4” if you aren’t careful about calling convention and .def file usage.

Keeping the exported function names in the symbol table free of such name-decoration comes in really handy when making GetProcAddress() calls as part of loading and hooking into a DLL explicitly at runtime. i.e. to get a pointer to the above function foo() (assuming it was exported at all) at runtime, you ideally just want to call:

HANDLE dllHandle = LoadLibrary("mydll.dll");
void* fooFcnPtr = GetProcAddress(dllHandle, "foo");

With some appropriate error case checking of course!

Use of a .def file plus __stdcall, __declspec(dllexport) and extern “C” on your function declarations when building your DLL will ensure that the above client-side code will work for a wide range of compilers and compiler settings.

More Related Contents:

  1. How to make a .lib file when have a .dll file and a header file
  2. When to use dynamic vs. static libraries
  3. Application failed to start because it could not find or load the QT platform plugin “windows”
  4. Win32 API to enumerate dll export functions?
  5. Registering a CPP dll into COM after installation using Wix Msi installer
  6. C++ DLL Export: Decorated/Mangled names
  7. How do I programmatically get the version of a DLL or EXE file?
  8. Altering DLL search path for static linked DLL
  9. Difference between shared objects (.so), static libraries (.a), and DLL’s (.so)?
  10. know if .lib is static or import
  11. Get DLL path at runtime
  12. DLL redirection using manifests
  13. How do I use a third-party DLL file in Visual Studio C++?
  14. AllocConsole() not displaying cout
  15. what does __declspec(dllimport) really mean?
  16. Is there a way to find all the functions exposed by a dll
  17. How to export a C++ class from a dll? [duplicate]
  18. DLL References in Visual C++
  19. Excel VBA, Can’t Find DLL Entry Point from a DLL file
  20. How can I use Standard Library (STL) classes in my dll interface or ABI?
  21. Why does this program crash: passing of std::string between DLLs
  22. Memory allocation and deallocation across dll boundaries
  23. What’s the differences between .dll , .lib, .h files?
  24. Get signatures of exported functions in a DLL
  25. Windows & C++: extern & __declspec(dllimport)
  26. Using shared_ptr in dll-interfaces
  27. Passing reference to STL vector over dll boundary
  28. C++ How to compile dll in a .exe
  29. C++ Passing std::string by reference to function in dll
  30. C++ static variable in .lib does not initialize

Leave a Comment