Quote:
Originally Posted by snarkophilus
I guess in the normal Windows environment, those warnings just go nowhere?
|
They go somewhere, just not to the detached terminal. Fancy debug servers can be configured to capture them, though. Trust me: it makes debugging on Windows difficult. With Linux and Mac, one can simply place a qDebug() statement in the code and have it displayed. Not so on Windows. At least not until I just learned that Cygwin's bash terminal captures them, that is!
I worry about what cygwin packages you may have installed that are on the system path, though. Are you just using Cygwin for a bash shell, or do you have any packages like Qt5 or Ssl installed? I tend to use MSYS2/MinGW for any bash-related Windows stuff. I'll have to see if the same is true for that bash shell on windows.