View Single Post
Old 22nd February 2010, 23:16   #6
Junior Member
Join Date: Jan 2003
Posts: 27
DialogEx for Unicode can be found at

For nsis plugins, generally disable all runtime checks, exceptions, etc, don't include default libs, then enable optimizations, link with pluginapi.c (in unicode nsis source), change most char to TCHAR, check for any calls to windows functions explicitly ending with A, they may be ok or may need to drop the A, wrap character and string constants with _T() or equiv, if it has exdll.h replace it with an include to pluginapi.h, either supply a mini-c-library or replace c library calls with the equiv from standard windows DLLs, eg #define strcpy lstrcpy; after some minor review & fixes, test to ensure everything works as expected and you will have a plugin that can be compiled as ANSI or (by defining UNICODE) as UNICODE.
PerditionC is offline   Reply With Quote