Mercurial > sdl-ios-xcode
view README.Qtopia @ 1550:31c2b8e4885e
Fixed bug #166
From the autoconf obsolete macros documentation:
Macro: AC_CANONICAL_SYSTEM
Determine the system type and set output variables to the names of the canonical system types. See section Getting the Canonical System Type, for details about the variables this macro sets.
The user is encouraged to use either AC_CANONICAL_BUILD, or AC_CANONICAL_HOST, or AC_CANONICAL_TARGET, depending on the needs. Using AC_CANONICAL_TARGET is enough to run the two other macros.
From the documentation for the canonical environments:
case $target in
i386-*-mach* | i386-*-gnu*)
obj_format=aout emulation=mach bfd_gas=yes ;;
i960-*-bout) obj_format=bout ;;
esac
Note that the above example uses $target because it's taken from a tool which can be built on some architecture ($build), run on another ($host), but yet handle data for a third architecture ($target). Such tools are usually part of a compiler suite, they generate code for a specific $target.
However $target should be meaningless for most packages. If you want to base a decision on the system where your program will be run, make sure you use the $host variable.
author | Sam Lantinga <slouken@libsdl.org> |
---|---|
date | Sun, 19 Mar 2006 05:27:22 +0000 |
parents | 2c5d4c22a2ac |
children |
line wrap: on
line source
============================================================================== Using the Simple DirectMedia Layer with Qtopia/OPIE ============================================================================== ============================================================================== I. Setting up the Qtopia development environment. This document will not explain how to setup the Qtopia development environment. That is outside the scope of the document. You can read more on this subject in this excellent howto: http://www.zauruszone.com/howtos/linux_compiler_setup_howto.html ============================================================================== II. Building the Simple DirectMedia Layer libraries using the arm cross-compiler This is somewhat tricky since the name of the compiler binaries differ from the standard. Also you should disable features not needed. The command below works for me. Note that it's all one line. You can also set the NM, LD etc environment variables separately. NM=arm-linux-nm LD=arm-linux-ld CC=arm-linux-gcc CXX=arm-linux-g++ RANLIB=arm-linux-ranlib AR=arm-linux-ar ./configure --enable-video-qtopia --disable-video-dummy --disable-video-fbcon --disable-video-dga --disable-arts --disable-esd --disable-alsa --disable-cdrom --disable-video-x11 --disable-nasm --prefix=/opt/Qtopia/sharp/ arm-unknown-linux-gnu One thing to note is that the above configure will include joystick support, even though you can't have joysticks on the Zaurus. The reason for this is to avoid link / compile / runtime errors with applications that have joystick support. ============================================================================== III. Building the Simple DirectMedia Layer test programs: After installing, making sure the correct sdl-config is in your path, run configure like this: NM=arm-linux-nm LD=arm-linux-ld CC=arm-linux-gcc CXX=arm-linux-g++ AR=arm-linux-ar ./configure arm-unknown-linux-gnu ============================================================================== IV. Application porting notes One thing I have noticed is that applications sometimes don't exit correctly. Their icon remains in the taskbar and they tend to relaunch themselves automatically. I believe this problem doesn't occur if you exit your application using the exit() method. However, if you end main() with 'return 0;' or so, this seems to happen. Also note that when running in landscape mode - i.e requesting a window that is HEIGHT pixels wide and WIDTH pixels high, where WIDTH and HEIGHT normally is 240 and 320 - the image is blitted so that the hardware buttons are on the left side of the display. This might not always be desirable but such is the code today. ============================================================================== V. Enjoy! :) If you have a project you'd like me to know about, or want to ask questions, go ahead and join the SDL developer's mailing list by sending e-mail to: sdl-request@libsdl.org and put "subscribe" into the subject of the message. Or alternatively you can use the web interface: http://www.libsdl.org/mailman/listinfo/sdl ============================================================================== VI. What is supported: Keyboard (Sharp Zaurus) Hardware buttons Stylus input (mouse) Video. Allows fullscreen both in portrait mode (up to WIDTHxHEIGHT size window) and in landscape mode (up to HEIGHTxWIDTH). All other SDL functionality works like a normal Linux system (threads, audio etc). -- David Hedbor <david@hedbor.org> http://david.hedbor.org/ http://eongames.com/