View Single Post
Old 31st July 2012, 07:31   #1
Junior Member
Join Date: Jul 2012
Posts: 5
Question Why the signature of NSIS plugin doesn't match the one in the script?

Hi all,
I'm new to NSIS, and try to wrapper the custom control written in C++ as a dll/plugin and call the related api from nsis script, however, i do notice that in the nsis example, the InstallOptions plugin which have a C++ signature just like

extern "C" void __declspec(dllexport) dialog(HWND hwndParent, int string_size,
char *variables, stack_t **stacktop)

however, it just called in a script(testlink.nsi) like
InstallOptions::dialog "$PLUGINSDIR\test.ini"

Why the signature doesn't match with their counterpart? What have happened in the NSIS source code underbeneath?

whossa is offline   Reply With Quote