On 12 Oct 2007, at 18:08, darby johnston wrote: > I'm using FLTK 1.1.x for a couple of applications that have both a > GUI and command line interface; this works great on UNIX, but not > so well on Windows: > >> WIN32 applications without a console cannot write to stdout or >> stderr, >> even if they are run from a console window. Any output is silently >> thrown away. > > I think the options still get passed, but you can't print out a > help screen or any error messages. Are there any way workarounds > for this without having the application pop-up it's own console?
Very much in the "workarounds" department... If you invoke your apps from an Msys shell (part of mingw) rather than from a DOS box, then stdout/stderr are *not* dropped, and it behaves much as a unix shell does. But that's probably not all that useful to you, I'd guess. Compiling as a "console" app I think does much the same, even for a DOS box - note that even though it is a "console" app, it can still run the GUI normally. I'm not not really clear on what the "console" option really changes, short of not making it drop stdout... -- Ian _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
