No output from devilutionx with --verbose on windows

[qndel]

Important information
Operating system / DevilutionX version / did you download a release or did you compile yourself?
Windows 10, compiled x64 debug build with visual studio 2019 - 9536927

Describe
Running devilutionx.exe --verbose from cmd or .bat script doesn't generate any output

To Reproduce
run devilutionx.exe --verbose from command line or a script

Expected behavior
Running devilutionx.exe --verbose should print some stuff

Additional context
devilutionx.exe --help
prints stuff correctly, so it shouldn't be an issue with printing stuff to console like before

[StephenCWills]

The SDL log output just doesn't go to stderr on Windows.
https://wiki.libsdl.org/CategoryLog

Here's where the messages go on different platforms:

||Windows||debug output stream||
||Android||log output||
||PSP||"SDL_Log.txt"||
||Others||standard error output (stderr)||

Although, I was able to pipe log output to a file with devilutionx.exe --verbose 2> log.txt so I'm not entirely sure what SDL is doing under the covers there.

Also, we do have the option of changing the default log output function.
https://wiki.libsdl.org/SDL_LogSetOutputFunction

[StephenCWills]

So it seems that SDL is doing everything it needs to in order to write to stderr.
https://github.com/libsdl-org/SDL/blob/6cd444f0fab9f7af501e76705b3dd77a4bbea10a/src/SDL_log.c#L376-L384

Their logic in that function actually matches very closely with how our printInConsole() function does things. However, the problem here seems to be that vcpkg ends up defining HAVE_STDIO_H when building SDL so this function compiles with fprintf() instead.
https://github.com/libsdl-org/SDL/blob/6cd444f0fab9f7af501e76705b3dd77a4bbea10a/src/SDL_log.c#L433-L434

I am presuming DevilutionX is compiled with /SUBSYSTEM:WINDOWS. I suspect that is the reason why fprintf() doesn't work unless stderr is explicitly piped to a file.
https://docs.microsoft.com/en-us/cpp/build/reference/subsystem-specify-subsystem?view=msvc-170

FYI, I've confirmed that the test builds do produce messages back to the console. It seems this issue does not affect the prebuilt SDL binaries used by CI.

[AJenbo]

Is this relevant? #3805

[StephenCWills]

Our backports use those two functions to implement the SDL2 logging API.

https://github.com/diasurgical/devilutionX/blob/b6617b0120b3fbbdfed24dae19d7d32189065f56/Source/utils/sdl2_to_1_2_backports.cpp#L163-L171

So I can think of a few different ways in which it's relevant, but the change in that PR doesn't have much affect on SDL2 builds. Also, the vcpkg library has no problem printing messages to the output window in Visual Studio. It's the other part that prints to stderr that gets compiled out.