Hi, I think you might want to read the article at the following link - it suggests placing mainCRTStartup in the "entry point" field in Linker/Advanced and setting Linker/Subsystem setting to "Windows" in Release mode with NO CHANGE to code - that is, keeping main() function as it is. I guess FLTK can do the same (?) I haven't tested this yet - just posting my thoughts directly. If you find it of any benefit then I guess you should update FLTK Programmer's Manual accordingly so that new users can get up to speed with FLTK fast.
http://live.gnome.org/gtkmm/MSWindows/UsingMSVC Best regards, Asif On Tue, May 24, 2011 at 8:23 PM, Greg Ercolano <[email protected]> wrote: > Albrecht Schlosser wrote: > > On 24.05.2011 11:32, asif saeed wrote: > > > >>> FL/winmain.h: > >>> > >>> #ifdef FL_DLL > >>> #include<Windows.h> > >>> // int main (int, char **); // should probably not be here ? > >>> int WINAPI WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, > >>> LPSTR lpCmdLine, int nCmdShow) { > >>> return main(__argc,__argv); > >>> } > >>> #endif // FL_DLL > >>> > >> May be you can name such header dll_linked_app.h or something like that. > > > > I think that winmain.h is a good choice, isn't it? > > Although we seem to be close to resolution.. > > I'd like to move this thread over to fltk.development, > subject: "Dynamic linking with VS 2010" > > (Asif, feel free to follow us over there.. fltk.development > is a group specifically for discussion of design of FLTK > which is public just like fltk.general) > _______________________________________________ > fltk mailing list > [email protected] > http://lists.easysw.com/mailman/listinfo/fltk > _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
