Matt: note that on Windows we had to create a separate fluid-cmd exe built with /subsystem:console for the command line version of fluid so that it works properly in Makefiles.. not because of the GUI stuff, but because a /subsystem:windows will (a) background itself and thereby can't return exit codes, and (b) can't properly interact via stdin/stdout with the dos window terminal the program was invoked from.

Not sure if the new admin tool falls into this category, but sounds like it might if it's something that could be called from a scripting context like a batch file, Makefile, perl/python/etc, so it should probably generate a separate xyz-cmd.exe on windows too, similar to fluid.

Building with /subsystem:console isn't a solution either because then when users click on that app, a separate DOS window provided by the OS is opened (for stdin/out), so we really had to go with separate binaries.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <fltk/fltk/pull/560/c1328300401@github.com>