Mercurial > sdl-ios-xcode
view test/automated/README @ 4426:1bceff8f008f
Fixed bug #943
Ozkan Sezer 2010-02-06 12:31:06 PST
Hi:
Here are some small fixes for compiling SDL against mingw-w64.
(see http://mingw-w64.sourceforge.net/ . Despite the name, it
supports both win32 and win64.)
src/audio/windx5/directx.h and src/video/windx5/directx.h (both
SDL-1.2 and SDL-1.3.) I get compilation errors about some union
not having a member named u1 and alike, because of other system
headers being included before this one and them already defining
DUMMYUNIONNAME and stuff. This header probably assumes that those
stuff are defined in windef.h, but mingw-w64 headers define them
in _mingw.h. Easily fixed by moving NONAMELESSUNION definition to
the top of the file.
src/thread/win32/SDL_systhread.c (both SDL-1.2 and SDL-1.3.) :
The __GNUC__ case for pfnSDL_CurrentBeginThread is 32-bit centric
because _beginthreadex returns uintptr_t, not unsigned long which
is 32 bits in win64. Changing the return type to uintptr_t fixes
it.
video/SDL_blit.h (and configure.in) (SDL-1.3-only) : MinGW-w64
uses msvcrt version of _aligned_malloc and _aligned_free and
they are defined in intrin.h (similar to VC). Adding proper
ifdefs fixes it. (Notes about macros to check: __MINGW32__ is
defined for both mingw.org and for mingw-w64 for both win32 and
win64, __MINGW64__ is only defined for _WIN64, so __MINGW64__
can't be used to detect mingw-w64: including _mingw.h and then
checking for __MINGW64_VERSION_MAJOR does the trick.)
SDL_win32video.h (SDL-1.3-only) : Tweaked the VINWER definition
and location in order to avoid multiple redefinition warnings.
Hope these are useful. Thanks.
author | Sam Lantinga <slouken@libsdl.org> |
---|---|
date | Wed, 10 Mar 2010 15:02:58 +0000 |
parents | 22ac66da0765 |
children |
line wrap: on
line source
SDL Automated Testing Framework User Documentation by Edgar Simo Serra Abstract The SDL Automated Testing Framework, hereby after called SDL_AT, is a meant to test the SDL code for regressions and other possible failures. It can also be used to display what your SDL set up supports. Basics The main way to use the framework is to compile it and run it, that can be done with the following command: $> make test It should then display something like: Platform : All tests successful (2) SDL_RWops : All tests successful (5) SDL_Surface : All tests successful (6) Rendering with x11 driver : All tests successful (4) Indicating that all tests were successful. If however a test fails output it will report the failure to stderr indicating where and why it happened. This output can then be sent to the developers so they can attempt to fix the problem. Advanced By passing the "-h" or "--help" parameter to testsdl you can get an overview of all the possible options you can set to furthur tweak the testing. A sample of the options would be the following: Usage: ./testsdl [OPTIONS] Options are: -m, --manual enables tests that require user interaction --noplatform do not run the platform tests --norwops do not run the rwops tests --nosurface do not run the surface tests --norender do not run the render tests -v, --verbose increases verbosity level by 1 for each -v -q, --quiet only displays errors -h, --help display this message and exit Developers See SDL_at.h for developer information.