mirror of
https://github.com/yawut/SDL.git
synced 2026-08-01 16:04:37 -05:00
SDL2 for the Nintendo Wii U (build with "cmake [SDL source path] -DCMAKE_TOOLCHAIN_FILE=$WUT_ROOT/share/wut.toolchain.cmake -DCMAKE_INSTALL_PREFIX=$DEVKITPRO/portlibs/wiiu")
2da6fd7637
t.grundner@goto3d.de 2011-09-01 03:59:17 PDT I figured out what is going on. GCC 4.5.2 assumes the stack is 16 byte aligned by default. Therefore there are no AND alignment corrections necessary if we wish to align a stack variable to a 16 byte boundary. That is bad if your OS ABI is not 16 byte aligned. Windows 32 bit stacks are 4 byte aligned. This results in the above mentioned SIGSEGV. This is also no problem if I compile both SDL.dll and my app with MingW because MinGW/GCC inserts a andl $-16, %esp instruction right in the beginning of the main function. So at least the stack of the thread calling the main function is 16 byte aligned. But as soon as I start to use the SDL.dll from an application not compiled by MinGW there is no ANDL safing my app. However there is a GCC option that can change the default stack alignment: -mpreferred-stack-boundary=num Setting num=2 assumes a the stack is aligned to a 4 byte boundary. This results in GCC inserting the necessary andl $-16, %esp into SDL_FillRect. Rebuilding SDL with ./configure "CFLAGS=-mpreferred-stack-boundary=2 -g -O3" solved the problem. IMHO this should also be a problem on Solaris. The following links contain further information: http://gcc.gnu.org/onlinedocs/gcc-4.5.2/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options http://www.agner.org/optimize/calling_conventions.pdf |
||
|---|---|---|
| acinclude | ||
| android-project | ||
| build-scripts | ||
| include | ||
| src | ||
| test | ||
| VisualC | ||
| Xcode | ||
| Xcode-iPhoneOS | ||
| .DISABLED-hgeol | ||
| .hgignore | ||
| .hgtags | ||
| .indent.pro | ||
| aclocal.m4 | ||
| Android.mk | ||
| autogen.sh | ||
| Borland.html | ||
| Borland.zip | ||
| BUGS | ||
| configure | ||
| configure.in | ||
| COPYING | ||
| CREDITS | ||
| INSTALL | ||
| Makefile.ds | ||
| Makefile.in | ||
| Makefile.minimal | ||
| Makefile.pandora | ||
| Makefile.wiz | ||
| NOTES | ||
| README | ||
| README-SDL.txt | ||
| README.android | ||
| README.BeOS | ||
| README.DirectFB | ||
| README.ds | ||
| README.gesture | ||
| README.HG | ||
| README.iphoneos | ||
| README.MacOSX | ||
| README.pandora | ||
| README.Platforms | ||
| README.Porting | ||
| README.touch | ||
| README.Watcom | ||
| README.WinCE | ||
| sdl-config.in | ||
| sdl.m4 | ||
| sdl.pc.in | ||
| SDL.spec.in | ||
| TODO | ||
| UNDER_CONSTRUCTION.txt | ||
| VisualC.html | ||
| Watcom-Win32.zip | ||
| WhatsNew | ||
Simple DirectMedia Layer
(SDL)
Version 1.3
---
http://www.libsdl.org/
This is the Simple DirectMedia Layer, a general API that provides low
level access to audio, keyboard, mouse, joystick, 3D hardware via OpenGL,
and 2D framebuffer across multiple platforms.
The current version supports Windows, Windows CE, Mac OS X, Linux, FreeBSD,
NetBSD, OpenBSD, BSD/OS, Solaris, iOS, and Android. The code contains
support for other operating systems but those are not officially supported.
SDL is written in C, but works with C++ natively, and has bindings to
several other languages, including Ada, C#, Eiffel, Erlang, Euphoria,
Go, Guile, Haskell, Java, Lisp, Lua, ML, Objective C, Pascal, Perl, PHP,
Pike, Pliant, Python, Ruby, and Smalltalk.
This library is distributed under the zlib license, which can be found
in the file "COPYING".
The best way to learn how to use SDL is to check out the header files in
the "include" subdirectory and the programs in the "test" subdirectory.
The header files and test programs are well commented and always up to date.
More documentation is available in HTML format in "docs/index.html", and
a documentation wiki is available online at:
http://www.libsdl.org/cgi/docwiki.cgi
The test programs in the "test" subdirectory are in the public domain.
Frequently asked questions are answered online:
http://www.libsdl.org/faq.php
If you need help with the library, or just want to discuss SDL related
issues, you can join the developers mailing list:
http://www.libsdl.org/mailing-list.php
Enjoy!
Sam Lantinga (slouken@libsdl.org)