https://bugs.winehq.org/show_bug.cgi?id=56459
--- Comment #7 from Eric Pouech eric.pouech@gmail.com --- (In reply to renatopereyra from comment #5)
Thanks for debugging this, Eric! I'm sorry I took a while to get back to you.
./wine [[your exec and args]] < /dev/null 2>&1 | cat -
This worked locally whenever the app does not have a console.
- Is there a way to get the output to (also) print to the Linux side even
when there is a console?
the command above ensures that: - wine is started without a (unix) console - but first program has its I/O stream bound to the unix fd (here 1,2 of wine program are printed to unix 1) - if first program starts another GUI program, the Windows default behavior is that the streams are *NOT* inherited by second (and subsequent program) - under certain conditions, Wine starts first a dedicated program (start.exe); if you're in that case, your launched app will not be able to print - you can test if its the case by ensuring that you use the full path to your application on command line
2 It seems a bit unsafe to rely on this long-term. Is there or could there be some kind of test in Wine that protects this kind of use/behavior?
what do you mean?