Relintai/sdl2_frt
1
0
Fork 0
mirror of https://github.com/Relintai/sdl2_frt.git synced 2024-12-25 09:17:12 +01:00
Code Issues Packages Projects Releases Wiki Activity
b88ca1b4a6
sdl2_frt/docs/README-porting.md
Edward Rudd b88ca1b4a6 the last parameter of XChangeProperty is the number of elements.. and when the element format is 32.. the element is "long" so we have 5 long elements here. 
Yes this seems confusing as on mac+linux Long is either 32 or 64bits depending on the architecture, but this is how the X11 protocol is defined. Thus 5 is the correct value for the nelts here.  Not 5 or 10 depending on the architecture.

More info on the confusion https://bugs.freedesktop.org/show_bug.cgi?id=16802
2015-02-10 16:28:56 -05:00

1.9 KiB
Raw Blame History

Porting

  • Porting To A New Platform

    The first thing you have to do when porting to a new platform, is look at include/SDL_platform.h and create an entry there for your operating system. The standard format is PLATFORM, where PLATFORM is the name of the OS. Ideally SDL_platform.h will be able to auto-detect the system it's building on based on C preprocessor symbols.

There are two basic ways of building SDL at the moment:

  1. The "UNIX" way: ./configure; make; make install

    If you have a GNUish system, then you might try this. Edit configure.in, take a look at the large section labelled: "Set up the configuration based on the host platform!" Add a section for your platform, and then re-run autogen.sh and build!

  2. Using an IDE:

    If you're using an IDE or other non-configure build system, you'll probably want to create a custom SDL_config.h for your platform. Edit SDL_config.h, add a section for your platform, and create a custom SDL_config_{platform}.h, based on SDL_config.h.minimal and SDL_config.h.in

    Add the top level include directory to the header search path, and then add the following sources to the project: src/.c src/atomic/.c src/audio/.c src/cpuinfo/.c src/events/.c src/file/.c src/haptic/.c src/joystick/.c src/power/.c src/render/.c src/stdlib/.c src/thread/.c src/timer/.c src/video/.c src/audio/disk/.c src/audio/dummy/.c src/video/dummy/.c src/haptic/dummy/.c src/joystick/dummy/.c src/main/dummy/.c src/thread/generic/.c src/timer/dummy/.c src/loadso/dummy/*.c

Once you have a working library without any drivers, you can go back to each of the major subsystems and start implementing drivers for your platform.

If you have any questions, don't hesitate to ask on the SDL mailing list: http://www.libsdl.org/mailing-list.php

Enjoy! Sam Lantinga (slouken@libsdl.org)