You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No stdout, no stderr, no error message printed if just .\chip8.exe is executed.
No stdout/stderr is because of -mwindows, which is a flag required to treat the application as a graphical (Win32) application instead of a console application. The deal is that unless the application is graphic, Windows will suck stdout/stderr and not print it to cmd.exe (MSYS shell works fine here).
No errors mean no feedback. If the user just double clicks chip8.exe icon he won't notice what is going on because there is no way for telling the user what he is supposed to do (drag a ROM icon to the application?, provide an argument via terminal?).
The text was updated successfully, but these errors were encountered:
No stdout, no stderr, no error message printed if just
.\chip8.exe
is executed.No stdout/stderr is because of
-mwindows
, which is a flag required to treat the application as a graphical (Win32) application instead of a console application. The deal is that unless the application is graphic, Windows will suck stdout/stderr and not print it to cmd.exe (MSYS shell works fine here).No errors mean no feedback. If the user just double clicks chip8.exe icon he won't notice what is going on because there is no way for telling the user what he is supposed to do (drag a ROM icon to the application?, provide an argument via terminal?).
The text was updated successfully, but these errors were encountered: