| Re: [hatari-devel] Hatari help output on Windows |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
Hi,
On 11/11/20 8:47 AM, Christian Zietz wrote:
Eero Tamminen schrieb:
Could somebody building Hatari for Windows comment on this?
There's not much to comment really. It's true. When building an
executable for the GUI subsystem, there is no console output. There
might not even be a console, if the .exe is launched e.g. by
double-clicking in the Explorer. And if the .exe is launched from the
command line, it detaches from the console. (This is BTW why Hatari has
the -W option for the debugger.)
Since I build Hatari myself, I changed the linker flags to build for the
console subsytem: -mconsole. Before that, I always patched that field in
the header [1] of Hatari binaries with a hexeditor. Note that this has
the side-effect of *opening* a console window when Hatari is not started
from the console, which might confuse users.
I see. In that case it's probably best just to add some note for
Windows users to the Hatari
readme & manual, like this:
---------------------------------------------
X) Known Windows problems
On Windows, Hatari console output doesn't go to
console like on other platforms.
This is because Windows SDL1 library redirects all
console output (including help!) to stdout.txt and
stderr.txt files by default, and SDL2 library
discard it.
To see Hatari help/warning/trace output, and
interact with Hatari debugger, there two options:
* Run Hatari with "-W" option
* Compile Hatari with "-mconsole"(as last
--linker flag) to build Hatari for the Windows
console subsystem
Because these cause separate console output window
to be opened in addition to Hatari window, they
are not enabled by default.
-------------------------------------------
Does above look correct?
- Eero