proposed solution for "#436 Output should be directed to the windows console"

[Thiago Macieira]

Em qua 19 mar 2014, às 09:15:20, Dirk Hohndel escreveu:
> On Wed, 2014-03-19 at 21:19 +0600, Farzana Raisa wrote:
> > I am not being able to cross compile on linux for windows. And I have
> > discussed about it in the list. That's why i couldn't compile it in
> > window. But i guess the problem will be solved if i use
> > fprintf(stderr, "") instead of printf("") in the function "static void
> > print_help()" and "static void print_version()" under the
> > subsurfacestartup.c file.
> 
> No. Windows doesn't connect stderr or stdout for UI applications.
> So this won't help at all.

stdout and stderr for a GUI application should be used for messages intended 
for us -- the developers -- not to the users. At best, we can ask them to run 
the application in a terminal and gather the output when doing bugfixing. 
Otherwise, it's unreasonable to expect them to see them at all.

On Linux desktops, the output is usually redirected to ~/.xsession-errors if 
you launch from the UI. On Windows, you can get the output by running 
dbgview.exe. On Mac OS X, there must be a way too but I don't know what it 
would be.

One exception to that rule is for output related to parsing the command-line: 
only users using a terminal will pass arguments on the command-line.
-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
   Software Architect - Intel Open Source Technology Center
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358