Question

I would like to have a DLL with window creation and management code in a way that the developer could just add a named main.h header and load the DLL to be able to instance a window.

#include "dllheader.h" 

void user_main();

main = user_main; // attach user main to the dll callback

int user_main() {
    Window *w = new Window();
}

on the DLL side the code should look like

void (*main)() = NULL;

int WinMain(...) {
   if(main)
       main(); // call the user defined funcion
   while(!done) {
       if(messageWaiting()) {
           processMessage();
       }
   }

}

Why? because I want to deploy a window wrapper and avoid to have the user writting the WinMain entry point. But a DLL project have a DLL main and a win32 project that uses a DLL complaim if linker doesnt find a winMain entry point.

Is there a know solution for this kind of arrange?

Answer 1

Every Win32 application must have an entry point (usally WinMain). So you can’t put the entry point in the DLL, because it’s not really part of the EXE. However the entry point can be in a statically linked library. When the static library gets linked, the entry point becomes part of the EXE.

But my suggestion is to avoid all this complexity. Just make the users of your DLL call something like this:

int WinMain( HINSTANCE hInstance, HINSTANCE hPrev, LPSTR lpCmdLine, int nCmdShow )
{
    return WrapperDllMain( hInstance, hPrev, lpCmdLine, nCmdShow, &user_main );
}

The code is simple and easy to write. It’s not much effort on the part of the DLL users. You have total control over the message loop (and the entire process lifetime).