Would I use SDL_Log*? Or do I have to write my own function? It seems SDL
still redirects cout and fprint from the terminal, and I just want to print
some debug informaiton that is useless if it’s not real time.
Any help would be great,
-Alex
Would I use SDL_Log*? Or do I have to write my own function? It seems SDL
still redirects cout and fprint from the terminal, and I just want to print
some debug informaiton that is useless if it’s not real time.
Any help would be great,
-Alex
Would I use SDL_Log*? Or do I have to write my own function? It seems
SDL still redirects cout and fprint from the terminal, and I just want
to print some debug informaiton that is useless if it’s not real time.
In SDL 1.2, set SDL_STDIO_REDIRECT=0 on the command line.
In SDL 1.3, it doesn’t look like we redirect at all anymore.
–ryan.
in win32, using std::cout from iostream in c++ seems to not produce any
output in any form whatsoever I checked for any files being created, or
msys terminal output, and I got nothing.
I’ll look into it more myself this evening and let you know if I find a
snag,
-AlexOn Wed, Oct 26, 2011 at 12:14 PM, Ryan C. Gordon wrote:
Would I use SDL_Log*? Or do I have to write my own function? It seems
SDL still redirects cout and fprint from the terminal, and I just want
to print some debug informaiton that is useless if it’s not real time.In SDL 1.2, set SDL_STDIO_REDIRECT=0 on the command line.
In SDL 1.3, it doesn’t look like we redirect at all anymore.
–ryan.
_____________**
SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/**listinfo.cgi/sdl-libsdl.orghttp://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org