Mini SDL C++
A set of typedefs for cleaner SDL in C++.
MiniSDL.hpp into your project, then slap the following two lines
into your relevant source file:
#include "MiniSDL.hpp" using namespace jpt;
Then look up the wrapper you need in MiniSDL.hpp.
Many other projects (e.g. SDLPP, RAGE::SDL, SDLmm, sdlxx) provide C++ wrappers for SDL, and I've never used any of them even though I've ported large C++ game engines of commercial studios to SDL. Most wrappers attempt to wrap the entire API of SDL, which means they almost always end up with one or more of these problems:
- Not having complete or up-to-date API coverage.
- Not having good documentation.
- Requiring re-learning the SDL API if you've used the C API before.
- Adding another chunky dependency on top of SDL.
- Complicating debugging by adding more layers between you and the API.
- Introducing bugs by adding more complexity.
SDL is used by a large number of commercial games, and has a thriving community of contributors. Odds are that your C++ wrapper of the day can't say the same.
In my opinion, SDL's API is straight forward and does not need to be C++ified. The one frustration with using SDL when writing C++ is that you need to manually manage object lifecycles and can't use nice C++-isms like having a SDL object that is destroyed when your stack frame ends.
All MiniSDLCPP does is manage the lifecycle of your objects. It has a simple C++
CDeleter) that calls a given C function on the argument, that is used as a
std::unique_ptr Deleter. It then has a series of typedefs (because it's a bit
messy) that you use to create
std::unique_ptrs with the right arguments to
manage SDL objects.
The API is simple:
obj.reset(handle)takes over the given handle, cleaning up any previous handle attached to this object.
obj.get()returns the handle.
obj.release()returns the handle, and tells the object to not clean up the handle when the object is destroyed.
The code is self-contained:
- One .hpp file
- Everything lives in the
- It builds with any modern C++11 compiler, no weird build options or external dependencies (but you supply the SDL.)