Mercurial > sdl-ios-xcode
view test/automated/README @ 3380:6f381d0d6394
stefanullinger to me
I updated and wanted to compile SDL, but it does not work.
The reason is the new pre-build step.
Currently it says:
"if exist $(SolutionDir)\..\include\SDL_config.h goto SDLCONFIGOKAY
echo Copying SDL_config_win32.h to SDL_config.h...
copy $(SolutionDir)\..\include\SDL_config_win32.h $(SolutionDir)\..\include\SDL_config.h
:SDLCONFIGOKAY
if exist $(SolutionDir)\..\include\SDL_revision.h goto SDLREVISIONOKAY
echo Creating stub SDL_revision.h file...
echo #define SDL_REVISION 0 >$(SolutionDir)\..\include\SDL_revision.h
:SDLREVISIONOKAY"
So ... the problem with this lines is, that they lookup the SolutionDir...
I think it should use the ProjectDir here!
I - for example - want to use SDL within my engine...
So my engine is the solutionDir...not SDL...SDL is just a sub-project.
I think you should change this, shouldn't you?!
Regards,
Stefan
author | Sam Lantinga <slouken@libsdl.org> |
---|---|
date | Sun, 11 Oct 2009 10:22:22 +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.