> the popular question reverse mode - I'm failing to create a > win32-console for debugging an old project with "printf"-debugging > output (WinXP and MinGW environment). The doc says, I would get the > console by fltk debug lib, so I used a "configure --enable-debug" to > make the debug lib and linked libfltkd.ato my app (okay, it doubles > size). No console in sight. I also tried "-mconsole" instead of > "-mwindows", but this creates a lot of missing functions.
If you build using mingw as you say, then the relevant options are, as you identified, -mwindows or -mconsole However, -mconsole is the default, so if you give neither option, then you should get a console. So in general, all you need to do is ensure that none of your compile or link commands (particularly the last link command) ever issue a -mwindows option and it "Just Works". So, I am thinking that the link line you are using must still have a -mwindows option it it somewhere. Also, as a slight aside, if you are using mingw, you should probably try the Msys shell rather than a dos box. The Msys shell works in such a way that, if you invoke your application from the shell, stdio *still works* even if your app was built with -mwindows. Which can be very handy for debug purposes. SELEX Sensors and Airborne Systems Limited Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
