the first plugin is using our framework, for the second ("test-against" plugin) looks like it happens with synthmaker, juce plugins. but yes different frameworks.
on our side the entry point is defined as:
Code:
__externc BOOL APIENTRY
DllMain(HINSTANCE hModule, DWORD reason, LPVOID lpReserved)
{
trace("win32 DllMain");
//g_Instance = hModule;
switch(reason)
{
case DLL_PROCESS_ATTACH:
trace("DllMain (reason: process attach)");
gWinInstance = hModule;
//printf("gWinInstance = %i\n",(int)gWinInstance);
break;
case DLL_PROCESS_DETACH:
trace("DllMain (reason: process detach)");
break;
case DLL_THREAD_ATTACH:
trace("DllMain (reason: thread attach)");
break;
case DLL_THREAD_DETACH:
trace("DllMain (reason: thread detach)");
break;
default:
trace("DllMain (reason: unknown)");
break;
}
return TRUE;
}
DllMain is mostly needed here to get the HINSTANCE hModule and retrieve the real path of the module.
[edit]: aha its the 'extern "C"' definition of the entry point.
but this is needed for LADSPA plugins on WIN32. a solution i guess is to make it format (vst / ladpsa / etc) specific.
--