SDL_Log and cygwin

SDL Development
1

Now that printf has been replaced with SDL_Log all over the test programs,
it would be nice if SDL_Log was clever enough to output to a cygwin
terminal. I see it will output to Window’s cmd.exe, but cygwin seems much
easier to use in my opinion.–
Terry Welsh
www.reallyslick.com

2

Works for me…

$ uname -srv
CYGWIN_NT-6.1-WOW64 1.7.23(0.268/5/3) 2013-08-09 10:09

$ ./testplatform.exe
INFO: This system is running Windows
INFO: All data types are the expected size.
INFO: Detected a little endian machine.
INFO: Value 16 = 0xCDAB, swapped = 0xABCD
INFO: Value 32 = 0xEFBEADDE, swapped = 0xDEADBEEF
INFO: Value 64 = 0xEFBEADDECDAB3412, swapped = 0x1234ABCDDEADBEEF
INFO: CPU count: 8
INFO: CPU cache line size: 64
INFO: RDTSC detected
INFO: AltiVec not detected
INFO: MMX detected
INFO: 3DNow! not detected
INFO: SSE detected
INFO: SSE2 detected
INFO: SSE3 detected
INFO: SSE4.1 detected
INFO: SSE4.2 detectedOn 8/15/2013 9:07 AM, Terry Welsh wrote:

Now that printf has been replaced with SDL_Log all over the test
programs, it would be nice if SDL_Log was clever enough to output to a
cygwin terminal. I see it will output to Window’s cmd.exe, but cygwin
seems much easier to use in my opinion.

Terry Welsh
www.reallyslick.com http://www.reallyslick.com

SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

3

Looks like I’m a little cursed.

$ uname -srv
CYGWIN_NT-6.1-WOW64 1.7.22(0.268/5/3) 2013-07-22 17:06

$ ./testplatform.exe

…and, crickets.

I guess this will have to go somewhere on my todo list, but I’m open to
suggestions.–
Terry Welsh
www.reallyslick.com

On Thu, Aug 15, 2013 at 9:37 AM, Andreas Schiffler wrote:

Works for me…

$ uname -srv
CYGWIN_NT-6.1-WOW64 1.7.23(0.268/5/3) 2013-08-09 10:09

$ ./testplatform.exe
INFO: This system is running Windows
INFO: All data types are the expected size.
INFO: Detected a little endian machine.
INFO: Value 16 = 0xCDAB, swapped = 0xABCD
INFO: Value 32 = 0xEFBEADDE, swapped = 0xDEADBEEF
INFO: Value 64 = 0xEFBEADDECDAB3412, swapped = 0x1234ABCDDEADBEEF
INFO: CPU count: 8
INFO: CPU cache line size: 64
INFO: RDTSC detected
INFO: AltiVec not detected
INFO: MMX detected
INFO: 3DNow! not detected
INFO: SSE detected
INFO: SSE2 detected
INFO: SSE3 detected
INFO: SSE4.1 detected
INFO: SSE4.2 detected

On 8/15/2013 9:07 AM, Terry Welsh wrote:

Now that printf has been replaced with SDL_Log all over the test programs,
it would be nice if SDL_Log was clever enough to output to a cygwin
terminal. I see it will output to Window’s cmd.exe, but cygwin seems much
easier to use in my opinion.

Terry Welsh
www.reallyslick.com

SDL mailing listSDL at lists.libsdl.orghttp://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

4

This is the type of mystery that makes me wish our software stacks had
fully-exposed and expandable debug stacks. Would be nice to be able to
compare automatically how Player 1 has a different setup from Player 2.On Thu, Aug 15, 2013 at 1:10 PM, Terry Welsh wrote:

Looks like I’m a little cursed.

$ uname -srv
CYGWIN_NT-6.1-WOW64 1.7.22(0.268/5/3) 2013-07-22 17:06

$ ./testplatform.exe

…and, crickets.

I guess this will have to go somewhere on my todo list, but I’m open to
suggestions.

Terry Welsh
www.reallyslick.com

On Thu, Aug 15, 2013 at 9:37 AM, Andreas Schiffler < aschiffler at ferzkopp.net> wrote:

Works for me…

$ uname -srv
CYGWIN_NT-6.1-WOW64 1.7.23(0.268/5/3) 2013-08-09 10:09

$ ./testplatform.exe
INFO: This system is running Windows
INFO: All data types are the expected size.
INFO: Detected a little endian machine.
INFO: Value 16 = 0xCDAB, swapped = 0xABCD
INFO: Value 32 = 0xEFBEADDE, swapped = 0xDEADBEEF
INFO: Value 64 = 0xEFBEADDECDAB3412, swapped = 0x1234ABCDDEADBEEF
INFO: CPU count: 8
INFO: CPU cache line size: 64
INFO: RDTSC detected
INFO: AltiVec not detected
INFO: MMX detected
INFO: 3DNow! not detected
INFO: SSE detected
INFO: SSE2 detected
INFO: SSE3 detected
INFO: SSE4.1 detected
INFO: SSE4.2 detected

On 8/15/2013 9:07 AM, Terry Welsh wrote:

Now that printf has been replaced with SDL_Log all over the test
programs, it would be nice if SDL_Log was clever enough to output to a
cygwin terminal. I see it will output to Window’s cmd.exe, but cygwin seems
much easier to use in my opinion.

Terry Welsh
www.reallyslick.com

SDL mailing listSDL at lists.libsdl.orghttp://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org