Logging on windows

[Tino]

Since the switch to SDL2 widelands does not create stderr.txt and stdout.txt any longer .

I've done some research, and it seems on windows it is decided at compile time (-mwindow vs. mconsole) if a program can log to stdout and if this is visible when the application is started in a commandshell.

My current goal is:
- If i call "widelands.exe --help || --version" in a windows commandshell i would like widelands to directly output the information into this console
- Running widelands.exe via startmenu -> current status quo, discard any output
- Running widelands.exe in a windows commandshell : output stdout and log into this console
- Running "widelands.exe --enable_log" log stdout and stderr into ~\.widelands\stdout.txt and stderr.txt

I've tried to implement the last use case in my branch, but now i am stuck:
- with enable_log both files get created at start
- only stderr.txt contains information on every run. stdout.txt does only contain information if i start widelands out of Codeblocks IDE. If i call the binary from a commandshell, stdout.txt stays empty.

[Tino (tino79)]

SirVer has fixed this for B19.

ToDo:
- Write the logfile to ~\.widelands and not into the install dir

[GunChleoc (gunchleoc)]

The logfile also seems to miss output from exceptions - do we need to generate a separate stderr.txt?

[GunChleoc (gunchleoc)]

@Tino: Are you happy with the current state of affairs, or do you wish for a more elaborate algorithm?

[Tino (tino79)]

Cool, thank you for implementing this!

There is still the problem, that STDERR gets lost in windows, error messages are neither printed to console nor to the stdout.txt.
But i think this is a SDL2 issue and maybe worth another bug...

[GunChleoc (gunchleoc)]

Thanks for your feedback, I have created a follow-up bug

https://bugs.launchpad.net/widelands/+bug/1792521

[GunChleoc (gunchleoc)]

Fixed in build20-rc1