Simple DirectMedia Layer

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

Lua error in package.lua at line 80: module 'strict' not found.

Simple DirectMedia Layer
File:Sdl-logo.png
SDL logo
Original author(s) Sam Lantinga
Developer(s) SDL Community
Initial release 1998; 26 years ago (1998)
Stable release 2.0.4[1] / 2 January 2016; 8 years ago (2016-01-02)[2]
Deprecated v1.2.15: 20 January 2012; 12 years ago (2012-01-20)
Written in C
Operating system Linux, Windows, OS X 10.4+, iOS 3.1.3+, Android 2.3.3+, FreeBSD 8.4+, Haiku
Additionally before v2.0.0 (deprecated versions): AmigaOS, RISC OS
Type API
License zlib License
Before 2.0.0:
GNU LGPL[3]
Website www.libsdl.org

Simple DirectMedia Layer (SDL) is a cross-platform software development library designed to provide a low level hardware abstraction layer to computer multimedia hardware components. Software developers can use it to write high-performance computer games and other multimedia applications that can run on many operating systems such as Android, iOS, Linux, Mac OS X, Windows and other platforms.[4]

SDL manages video, audio, input devices, CD-ROM, threads, shared object loading, networking and timers.[5] For 3D graphics it can handle an OpenGL or Direct3D context.

The library is internally written in C and Objective-C and provides the application programming interface in C, with bindings to other languages available.[6] It is free and open-source software subject to the requirements of the zlib License since version 2.0 and with prior versions subject to the GNU Lesser General Public License.[3] Under the zlib License, SDL 2.0 is freely available for static linking in closed-source projects, unlike SDL 1.2.[7]

SDL is extensively used in the industry in both large and small projects. Over 700 games, 180 applications, and 120 demos have also been posted on the library website.

A common misconception is that SDL is a game engine, but this is not true. However, the library is well-suited for building an engine on top of it.

History

Sam Lantinga created the library, first releasing it in early 1998, while working for Loki Software. He got the idea while porting a Windows application to Macintosh. He then used SDL to port Doom to BeOS (see Doom source ports). Several other free libraries were developed to work alongside SDL, such as SMPEG and OpenAL. He also founded Galaxy Gameworks in 2008 to help commercially support SDL, although the company plans are currently on hold due to time constraints.[8] Soon after putting Galaxy Gameworks on hold, Lantinga announced that SDL 1.3 (which would then later become SDL 2.0) would be licensed under the zlib License.[9] Lantinga announced SDL 2.0 on 14 July 2012, at the same time announcing that he was joining Valve Software, the first version of which was announced the same day he joined the company.[10] Lantinga announced the stable release of SDL 2.0.0 on 13 August 2013.[11]

SDL 2.0 is a major update to the SDL 1.2 codebase with a different, not backwards-compatible[12] API. It replaces several parts of the 1.2 API with more general support for multiple input and output options.

Some feature additions include multiple window support, hardware-accelerated 2D graphics, and better Unicode support.[13]

Support for Mir and Wayland was added in SDL 2.0.2[14] and enabled by default in SDL 2.0.4.[15]

Better support for Android in forthcoming 2.0.4.[16]

Software architecture

SDL is a wrapper around the operating-system-specific functions game engines needs to access. The only purpose of SDL is to provide a common framework for accessing these functions for multiple operating systems (cross-platform).[17] SDL provides support for 2D pixel operations, sound, file access, event handling, timing and threading. It is often used to complement OpenGL by setting up the graphical output and providing mouse and keyboard input, since OpenGL comprises only rendering.

A game using the Simple DirectMedia Layer will not automatically run on every operating system, further adaptations must be applied. These are reduced to the minimum, since SDL also contains a few abstraction APIs for frequent functions offered by an operating system.

The syntax of SDL is function-based: all operations done in SDL are done by passing parameters to subroutines (functions). Special structures are also used to store the specific information SDL needs to handle. There are a few different subsystems SDL categorizes its functions under.

SDL can be used instead of XInput and XAudio2.[citation needed]

Subsystems

SDL is divided into several subsystems:[18]

Basics
Initialization and Shutdown, Configuration Variables, Error Handling, Log Handling
Video
Display and Window Management, surface functions, rendering acceleration, etc.
Input Events
Event handling, Support for Keyboard, Mouse, Joystick and Game controller
Force Feedback
SDL_haptic.h implements support for "Force Feedback"
Audio
SDL_audio.h implements Audio Device Management, Playing and Recording
Threads
multi-threading: Thread Management, Thread Synchronization Primitives, Atomic Operations
Timers
Timer Support
File Abstraction
Filesystem Paths, File I/O Abstraction
Shared Object Support
Shared Object Loading and Function Lookup
Platform and CPU Information
Platform Detection, CPU Feature Detection, Byte Order and Byte Swapping, Bit Manipulation
Power Management
Power Management Status
Additional
Platform-specific functionality

Besides this basic, low-level support, there also are a few separate official libraries that provide some more functions. These comprise the "standard library", and are provided on the official website and included in the official documentation:

  • SDL_image — support for multiple image formats[19]
  • SDL_mixer — complex audio functions, mainly for sound mixing[20]
  • SDL_net — networking support[21]
  • SDL_ttf — TrueType font rendering support[22]
  • SDL_rtf — simple Rich Text Format rendering[23]

Other, non-standard libraries also exist. For example: SDL_Collide on Sourceforge created by Amir Taaki.

Language bindings

The SDL 2.0 library has language bindings for C, C++, Pascal,[6] Python (via PySDL2.0),[6] C#,[6] Lua,[6] OCaml,[6] Rust, Nim, Vala and Genie.

Supported back-ends

Abstraction layers of several SDL platforms

Because of the way SDL is designed, much of its source code is split into separate modules for each operating system, to make calls to the underlying system. When SDL is compiled, the correct modules are selected for the target system. Following back-ends are available:[24]

SDL 1.2 has support for RISC OS (dropped in 2.0).

Reception and adoption

Workshop on SDL, University of Cádiz

Over the years SDL was used for many commercial and non-commercial video game projects, for instance MobyGames listed 120 games using SDL in 2013[30] and the SDL website itself listed around 700 games in 2012.[31] Important commercial examples are Angry Birds[32] or Unreal Tournament, from the open source domain OpenTTD,[33] The Battle for Wesnoth[34] or Freeciv.[35]

The cross-platform game releases of the popular Humble Indie Bundles for Linux, Mac and Android are often SDL based.

SDL is also often used for later ports on new platforms with existing legacy code, for instance the PC game Homeworld was ported to the Pandora handheld[36] and Jagged Alliance 2 for Android[37] via SDL.

Also, several non video game software uses SDL, examples are the emulators DOSBox and VisualBoyAdvance.

There were several books written for the development with SDL (see further readings).

SDL is used in university courses teaching multimedia and computer science, for instance, in a workshop about game programming using libSDL at the University of Cadiz in 2010.

Video game examples using SDL

Lua error in package.lua at line 80: module 'strict' not found.

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: List of games using SDL

See also

References

  1. ↑ Simple DirectMedia Layer - SDL version 2.0.4 (stable). Libsdl.org (5 January 2001). Retrieved on 2016-01-03.
  2. ↑ Index of /release. Libsdl.org (17 August 2013). Retrieved on 2016-01-03.
  3. ↑ 3.0 3.1 Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  5. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ 6.0 6.1 6.2 6.3 6.4 6.5 Lua error in package.lua at line 80: module 'strict' not found.
  7. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ SDL 1.3 to be zLib Licensed, SDL Mailing List, 7 April 2011
  10. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  11. ↑ Announcing SDL 2.0.0, SDL Mailing List, 13 August 2013
  12. ↑ MigrationGuide - SDL Wiki'. Wiki.libsdl.org (21 November 2013). Retrieved on 2013-12-08.
  13. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  14. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  15. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  16. ↑ https://wiki.libsdl.org/SDL_SysWMinfo
  17. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  18. ↑ https://wiki.libsdl.org/APIByCategory
  19. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  20. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  21. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  22. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  23. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  24. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  25. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  26. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  27. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  28. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  29. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  30. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  31. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  32. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  33. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  34. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  35. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  36. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  37. ↑ JA2 Stracciatella Feedback » Jagged Alliance 2 Android Stracciatella Port RC2 Release - please test on the Bear's Pit Forum, 3 October 2011
  38. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  39. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  40. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  41. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  42. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  43. ↑ Lua error in package.lua at line 80: module 'strict' not found.

Further reading

External links

  • No URL found. Please specify a URL here or add one to Wikidata.
Retrieved from "https://infogalactic.com/w/index.php?title=Simple_DirectMedia_Layer&oldid=19193"