Bindings for SDL3 in Rust. Work in progress.
This is an interface to use SDL3 from Rust.
Low-level C components are wrapped in Rust code to make them more idiomatic and abstract away inappropriate manual memory management.
sdl3-rs uses the MIT license.
This is a fork of Rust-sdl2 migrated according to the SDL2->SDL3 migration guide.
If you want a library compatible with earlier versions of SDL, please see here or Rust-sdl2.
The following features are enabled in the documentation:
- gfx
- image
- mixer
- ttf
The unsafe_textures feature is not documented online, you can use cargo doc to generate your own documentation
with this feature enabled.
We currently target the latest stable release of Rust.
SDL3 is still in development so please do not expect stability yet.
This crate supports a feature named "bundled" which compiles SDL3 from source and links it automatically. While this should work for any architecture, you will need a C compiler (like gcc, clang, or MS's own compiler) to use this feature properly.
By default, macOS and Linux only load libraries from system directories like /usr/lib. If you wish to distribute the newly built libsdl3.so/libsdl3.dylib alongside your executable, you will need to add rpath to your executable. Add the following lines to build.rs script:
#[cfg(target_os="macos")]
println!("cargo:rustc-link-arg=-Wl,-rpath,@loader_path");
#[cfg(target_os="linux")]
println!("cargo:rustc-link-arg=-Wl,-rpath,$ORIGIN");Install these through your favourite package management tool, or via http://www.libsdl.org/
Ubuntu example:
sudo apt-get install libsdl3-dev
Fedora example:
sudo dnf install sdl3-devel
Arch example:
(Arch doesn't have separate regular and development packages, everything goes together.)
sudo pacman -S sdl3
You might also need a C compiler (gcc).
You can choose to link sdl3 statically instead of dynamically with the static-link feature.
On Linux, you will need to additionally do one of the following:
- use the
bundledfeature - use the feature
use-pkgconfigso that rustc knows where to look for your sdl3 libraries and its dependencies for static linking. This is required because there is no built-in way to find the resources needed to link statically sdl3 from your system - install development libraries with vcpkg. Instructions to generate a static binary on Linux and other operating systems using vcpkg are here
On macOS, it's a good idea to install these via homebrew.
brew install sdl3
In recent versions of Homebrew, the installed libraries are usually linked into $(brew --prefix)/lib.
If you are running an older version, the symlink for SDL might reside in /usr/local/lib.
To make linking libraries installed by Homebrew easier, do the following for your respective shell.
Add this line to your ~/.zshenv or ~/.bash_profile depending on whether you use ZSH or Bash.
export LIBRARY_PATH="$LIBRARY_PATH:$(brew --prefix)/lib"
You can also get sdl3 via macports.
sudo port install libsdl3
Then add the following to your ~/.bash_profile if not already present.
export LIBRARY_PATH="$LIBRARY_PATH:/opt/local/lib/"
If you're having issues with either Homebrew or MacPorts, see here.
You can download and install the sdl3 Mac OS X framework from: https://www.libsdl.org/download-2.0.php
To make the sdl3 crate link with the sdl3 framework, you will need to enable
the use_mac_framework feature. To build and test the sdl3 crate with this
feature, use:
cargo test --features use_mac_framework
To depend on the sdl3 crate with this feature enabled, put the following in
your project's Cargo.toml file:
[dependencies.sdl3]
features = ["use_mac_framework"]
version = ... # Whichever version you are usingAlternatively, you can re-export the feature in your package by putting the
following in your Cargo.toml file:
[features]
default = []
use_sdl3_mac_framework = ["sdl3/use_mac_framework"]Instructions to generate a static binary on macOS and other operating systems using vcpkg are here.
-
Download MSVC development libraries from http://www.libsdl.org/ (sdl3-devel-3.0.x-VC.zip).
-
Unpack sdl3-devel-3.0.x-VC.zip to a folder of your choosing (You can delete it afterwards).
-
Copy all lib files from
sdl3-devel-3.0.x-VC\sdl3-3.0.x\lib\x64\
to
C:\Program Files\Rust\lib\rustlib\x86_64-pc-windows-msvc\lib
or to your library folder of choice, and ensure you have a system environment variable of
LIB = C:\your\rust\library\folder
For Rustup users, this folder will be in
C:\Users\{Your Username}\.rustup\toolchains\{current toolchain}\lib\rustlib\{current toolchain}\lib
Where current toolchain is likely stable-x86_64-pc-windows-msvc.
-
Copy sdl3.dll from
sdl3-devel-3.0.x-VC\sdl3-3.0.x\lib\x64\
into your cargo project, right next to your Cargo.toml.
-
When you're shipping your game make sure to copy sdl3.dll to the same directory that your compiled exe is in, otherwise the game won't launch.
The MSVC development libraries provided by http://libsdl.org/ don't include a static library. This means that if you want to use the static-link feature with the windows-msvc toolchain, you have to do one of
- build an sdl3 static library yourself and copy it to your toolchain's
libdirectory; or - also enable the
bundledfeature, which will build a static library for you; or - use a static sdl3 library from vcpkg as described below.
-
Download mingw development libraries from http://www.libsdl.org/ (sdl3-devel-2.0.x-mingw.tar.gz).
-
Unpack to a folder of your choosing (You can delete it afterwards).
-
Copy all lib files from
sdl3-devel-2.0.x-mingw\sdl3-3.0.x\x86_64-w64-mingw32\lib
to (for Rust 1.6 and above)
C:\Program Files\Rust\lib\rustlib\x86_64-pc-windows-gnu\lib
or to (for Rust versions 1.5 and below)
C:\Program Files\Rust\bin\rustlib\x86_64-pc-windows-gnu\lib
or to your library folder of choice, and ensure you have a system environment variable of
LIBRARY_PATH = C:\your\rust\library\folder
For Rustup users, this folder will be in
C:\Users\{Your Username}\.rustup\toolchains\{current toolchain}\lib\rustlib\{current toolchain}\lib
Where current toolchain is likely stable-x86_64-pc-windows-gnu.
-
Copy sdl3.dll from
sdl3-devel-3.0.x-mingw\sdl3-3.0.x\x86_64-w64-mingw32\bin
into your cargo project, right next to your Cargo.toml.
-
When you're shipping your game make sure to copy sdl3.dll to the same directory that your compiled exe is in, otherwise the game won't launch.
If you want to use the static-link feature with the windows-gnu toolchain, then you will also need the following libraries:
libimm32.a
libversion.a
libdinput8.a
libdxguid.a
These files are not currently included with the windows-gnu toolchain, but can be downloaded here. For the x86_64 toolchain, you want the x86_64-win32-seh package, and for i686 you want the i686-win32-dwarf one.
You will find the aforementioned libraries under mingw64/x86_64-w64-mingw32/lib/ (for x86_64) or mingw32/i686-w64-mingw32/lib/ (for i686). Copy them to your toolchain's lib directory (the same one you copied the SDL .a files to).
- Download mingw and msvc development libraries from http://www.libsdl.org/ (sdl3-devel-2.0.x-mingw.tar.gz & sdl3-devel-2.0.x-VC.zip).
- Unpack to folders of your choosing (You can delete it afterwards).
- Create the following folder structure in the same folder as your Cargo.toml:
gnu-mingw\dll\32
gnu-mingw\dll\64
gnu-mingw\lib\32
gnu-mingw\lib\64
msvc\dll\32
msvc\dll\64
msvc\lib\32
msvc\lib\64
- Copy the lib and dll files from the source archive to the directories we created in step 3 like so:
sdl3-devel-2.0.x-mingw.tar.gz\sdl3-2.0.x\i686-w64-mingw32\bin -> gnu-mingw\dll\32
sdl3-devel-2.0.x-mingw.tar.gz\sdl3-2.0.x\x86_64-w64-mingw32\bin -> gnu-mingw\dll\64
sdl3-devel-2.0.x-mingw.tar.gz\sdl3-2.0.x\i686-w64-mingw32\lib -> gnu-mingw\lib\32
sdl3-devel-2.0.x-mingw.tar.gz\sdl3-2.0.x\x86_64-w64-mingw32\lib -> gnu-mingw\lib\64
sdl3-devel-2.0.8-VC.zip\sdl3-2.0.x\lib\x86\*.dll -> msvc\dll\32
sdl3-devel-2.0.8-VC.zip\sdl3-2.0.x\lib\x64\*.dll -> msvc\dll\64
sdl3-devel-2.0.8-VC.zip\sdl3-2.0.x\lib\x86\*.lib -> msvc\lib\32
sdl3-devel-2.0.8-VC.zip\sdl3-2.0.x\lib\x64\*.lib -> msvc\lib\64
-
Create a build script, if you don't already have one put this in your Cargo.toml under
[package]:build = "build.rs"
-
Create a file in the same directory as Cargo.toml called build.rs (if you didn't already have a build script) and paste this into it:
use std::env;
use std::path::PathBuf;
fn main() {
let target = env::var("TARGET").unwrap();
if target.contains("pc-windows") {
let manifest_dir = PathBuf::from(env::var("CARGO_MANIFEST_DIR").unwrap());
let mut lib_dir = manifest_dir.clone();
let mut dll_dir = manifest_dir.clone();
if target.contains("msvc") {
lib_dir.push("msvc");
dll_dir.push("msvc");
}
else {
lib_dir.push("gnu-mingw");
dll_dir.push("gnu-mingw");
}
lib_dir.push("lib");
dll_dir.push("dll");
if target.contains("x86_64") {
lib_dir.push("64");
dll_dir.push("64");
}
else {
lib_dir.push("32");
dll_dir.push("32");
}
println!("cargo:rustc-link-search=all={}", lib_dir.display());
for entry in std::fs::read_dir(dll_dir).expect("Can't read DLL dir") {
let entry_path = entry.expect("Invalid fs entry").path();
let file_name_result = entry_path.file_name();
let mut new_file_path = manifest_dir.clone();
if let Some(file_name) = file_name_result {
let file_name = file_name.to_str().unwrap();
if file_name.ends_with(".dll") {
new_file_path.push(file_name);
std::fs::copy(&entry_path, new_file_path.as_path()).expect("Can't copy from DLL dir");
}
}
}
}
}- On build the build script will copy the needed DLLs into the same directory as your Cargo.toml, you probably don't want to commit these to any Git repositories though so add the following line to your .gitignore file
/*.dll
- When you're publish your game make sure to copy the corresponding sdl3.dll to the same directory that your compiled exe is in, otherwise the game won't launch.
And now your project should build and run on any Windows computer!
- Install MS build tools and vcpkg
- Install the needed sdl3 libs:
vcpkg.exe install sdl3-ttf:x64-windows sdl3:x64-windows - Open a x64 native tools prompt (x64 Native Tools Command Prompt for VS 2019)
- set env vars:
SET PATH=%PATH%;C:\Users\my_user\dev\vcpkg\installed\x64-windows\bin
SET INCLUDE=%INCLUDE%;C:\Users\my_user\dev\vcpkg\installed\x64-windows\include
SET LIB=%LIB%;C:\Users\my_user\dev\vcpkg\installed\x64-windows\lib
cargo build
Another method of getting the development libraries is with vcpkg. To set up a project to build a static binary on Windows (MSVC), Linux or macOS that is buildable like this:
cargo install cargo-vcpkg
cargo vcpkg build
cargo buildadd the following your Cargo.toml:
[dependencies.sdl3]
version = "0.0.1"
default-features = false
features = ["ttf","image","gfx","mixer","static-link","use-vcpkg"]
[package.metadata.vcpkg]
dependencies = ["sdl3", "sdl3-image[libjpeg-turbo,tiff,libwebp]", "sdl3-ttf", "sdl3-gfx", "sdl3-mixer"]
git = "https://github.com/microsoft/vcpkg"
rev = "261c458af6e3eed5d099144aff95d2b5035f656b"
[package.metadata.vcpkg.target]
x86_64-pc-windows-msvc = { triplet = "x64-windows-static-md" }More information on the cargo vcpkg tool is here.
If you're using cargo to manage your project, you can download through Crates.io:
[dependencies]
sdl3 = "0.0.1"Alternatively, pull it from GitHub to obtain the latest version from master
[dependencies.sdl3]
git = "https://github.com/revmischa/sdl3-rs"Otherwise, clone this repo and run cargo
cargo build
You can enable features such as ttf, image, gfx and mixer by adding this instead:
[dependencies.sdl3]
version = "0.0.1"
default-features = false
features = ["ttf","image","gfx","mixer"]Those features need their respective libraries, which can be found at these locations: (the install process is the same as sdl3)
As of now, sdl3_net is meaningless compared to what other crates
such as serde and bincode can offer.
We highly recommend using those to develop anything UDP or TCP
related (along with futures or TCP/UDP from the standard library).
If you still want an implementation of sdl3_net, you can try to add it in this repo as a feature via a Pull Request. A somewhat outdated version of this binding can be found here
We have several simple example projects included:
cargo run --example demo
You can see the full list in the examples/ folder. Some examples require some features, you can enable them like so:
cargo run --example gfx-demo --features "gfx"
Replace "gfx" by the feature(s) needed for the example you want.
In the sdl3::render module, Texture has by default lifetimes to prevent it from out-living its parent TextureCreator.
These lifetimes are sometimes too hard to deal with in Rust, and so you have the option to enable the unsafe_textures feature.
This removes the lifetimes on the Textures, at the cost of optional manual memory management. If you want to manually destroy
the Textures you use, you can call the destroy method of your Textures, but beware that it should not be called if none of
the parents (Canvas or TextureCreator) are alive. If you do not call this method, the memory will simply be freed when
the last Canvas or the last TextureCreator will be freed.
There is no online documentation for this feature, however you can build it yourself in your project by enabling the feature in your
Cargo.toml, running cargo doc and accessing target/doc/sdl3/index.html via a browser.
The sdl3-sys that was generated for this crate is very generic and can be used on a lot of platforms with very few limitations. However, you may sometimes face trouble when using platform-specific features of sdl3, for instance the WindowManager category.
The feature "use-bindgen" allows you to avoid this limitation by generating the proper bindings depending on your target. It will take
the headers based on what pkg-config outputs (if you enabled the feature "use-pkg-config") and generate bindings based on them.
If you don't have pkg-config or disabled the feature, it will try to get the headers in SDL-2.0.8/include of this crate instead.
If somehow you have your own headers that you want to use (use a beta version, an older version, ...), you can set the environment variable "sdl3_INCLUDE_PATH" and those headers will be used by bindgen instead.
If you are creating a *-sys crate for a library which requires sdl3, you can use sdl3-sys to provide both the compiled library
and the headers for sdl3.
Follow the following process to get the header directory. In the Cargo.toml for your crate, add sdl3-sys as a dependency (not a build-dependency).
Cargo will then provide your build script with an environment variable DEP_sdl3_INCLUDE which is populated with the include directory for sdl3.
If there is more than one directory, they are combined with : as a separator. Pass these directories to whatever is building your C/C++.
Once everything is linked together, there will be a single copy of sdl3 (the one provided by sdl3-sys) for all C, C++, and Rust code.
For more discussion see the corresponding issue
There are two ways to use OpenGL:
- As a backend for sdl3::render, where everything is done for you by sdl3. It is the default for linux devices.
- Manually, using only sdl3 as a "shell" for your window (akin to
glutinandwinitcrates), and still use sdl3's joystick, events, audio, text input, ect capabilities.
If you want to use OpenGL, you also need the gl-rs package. If you're using cargo, just add these lines to your Cargo.toml:
[dependencies.gl]
git = "https://github.com/bjz/gl-rs"You have two options to use OpenGL with sdl3:
- Use OpenGL with Canvas and use sdl3::render
- Use OpenGL directly on the Window "shell" and use manual OpenGL calls to render something
First, find the OpenGL driver from SDL:
fn find_sdl_gl_driver() -> Option<u32> {
for (index, item) in sdl3::render::drivers().enumerate() {
if item.name == "opengl" {
return Some(index as u32);
}
}
None
}
fn main() {
let sdl_context = sdl3::init().unwrap();
let video_subsystem = sdl_context.video().unwrap();
let window = video_subsystem.window("Window", 800, 600)
.opengl() // this line DOES NOT enable opengl, but allows you to create/get an OpenGL context from your window.
.build()
.unwrap();
let canvas = window.into_canvas()
.index(find_sdl_gl_driver().unwrap())
.build()
.unwrap();
// ...
}If you don't plan to use OpenGL calls via the gl-rs crate, you can stop here. sdl3 will automatically use the OpenGL backend
If you plan to have your own calls intertwined with the sdl3 calls, you need to use the context of your canvas first:
// initialization
gl::load_with(|name| video_subsystem.gl_get_proc_address(name) as *const _);
// sdl::render creates a context for you, if you use a Canvas you need to use it.
canvas.window().gl_set_context_to_current();
// ... in the main loop ...
unsafe {
gl::ClearColor(0.6, 0.0, 0.8, 1.0);
gl::Clear(gl::COLOR_BUFFER_BIT);
}
canvas.present();Be wary though, sdl3 has its own internal state which you should avoid messing with. Avoid using manual OpenGL in the middle of sdl3 calls, or make sure to restore the previous state.
extern crate sdl3;
extern crate gl;
use sdl3::event::Event;
use sdl3::keyboard::Keycode;
use sdl3::video::GLProfile;
fn main() {
let sdl_context = sdl3::init().unwrap();
let video_subsystem = sdl_context.video().unwrap();
let gl_attr = video_subsystem.gl_attr();
gl_attr.set_context_profile(GLProfile::Core);
gl_attr.set_context_version(3, 3);
let window = video_subsystem.window("Window", 800, 600)
.opengl()
.build()
.unwrap();
// Unlike the other example above, nobody created a context for your window, so you need to create one.
let ctx = window.gl_create_context().unwrap();
gl::load_with(|name| video_subsystem.gl_get_proc_address(name) as *const _);
debug_assert_eq!(gl_attr.context_profile(), GLProfile::Core);
debug_assert_eq!(gl_attr.context_version(), (3, 3));
let mut event_pump = sdl_context.event_pump().unwrap();
'running: loop {
unsafe {
gl::ClearColor(0.6, 0.0, 0.8, 1.0);
gl::Clear(gl::COLOR_BUFFER_BIT);
}
window.gl_swap_window();
for event in event_pump.poll_iter() {
match event {
Event::Quit {..} | Event::KeyDown { keycode: Some(Keycode::Escape), .. } => {
break 'running
},
_ => {}
}
}
::std::thread::sleep(::std::time::Duration::new(0, 1_000_000_000u32 / 60));
}
}As mentionned above, this method is useful when you don't care about sdl3's render capabilities, but you do care about its audio, controller and other neat features that sdl3 has.
You don't have to worry about messing with the state intertwined with sdl3 or a version you don't like: sdl3 will never
call any OpenGL function outside the render module.
To use Vulkan, you need a Vulkan library for Rust. This example uses the Vulkano library. Other libraries may use different data types for raw Vulkan object handles. The procedure to interface sdl3's Vulkan functions with these will be different for each one.
extern crate sdl3;
extern crate vulkano;
use sdl3::event::Event;
use sdl3::keyboard::Keycode;
use std::sync::Arc;
use vulkano::instance::{Instance, InstanceCreateInfo, InstanceExtensions};
use vulkano::swapchain::{Surface, SurfaceApi};
use vulkano::{Handle, VulkanLibrary, VulkanObject};
fn main() {
let sdl_context = sdl3::init().unwrap();
let video_subsystem = sdl_context.video().unwrap();
let window = video_subsystem
.window("Window Title - My Vulkano-sdl3 application", 1024, 768)
.vulkan()
.build()
.unwrap();
let instance_extensions =
InstanceExtensions::from_iter(window.vulkan_instance_extensions().unwrap());
let instance = Instance::new(VulkanLibrary::new().unwrap(), {
let mut instance_info = InstanceCreateInfo::application_from_cargo_toml();
instance_info.enabled_extensions = instance_extensions;
instance_info
})
.unwrap();
let surface_handle = window
.vulkan_create_surface(instance.handle().as_raw() as _)
.unwrap();
// SAFETY: that's just the way it is
let surface = unsafe {
Surface::from_handle(
Arc::clone(&instance),
<_ as Handle>::from_raw(surface_handle),
SurfaceApi::Xlib,
None,
)
};
let mut event_pump = sdl_context.event_pump().unwrap();
'running: loop {
for event in event_pump.poll_iter() {
match event {
Event::Quit { .. }
| Event::KeyDown {
keycode: Some(Keycode::Escape),
..
} => {
break 'running;
}
_ => {}
}
}
::std::thread::sleep(::std::time::Duration::new(0, 1_000_000_000u32 / 60));
}
}
raw-window-handle can be enabled using the feature name:
[dependencies.sdl3]
version = "0.0.1"
features = ["raw-window-handle"]An example working with wgpu is also available:
cargo run --example raw-window-handle-with-wgpu --features raw-window-handleOn macOS the RawWindowHandle.ns_view field is returned null. Libraries consuming the RawWindowHandle (such as
wgpu) should determine a sane default for ns_view. If they do not, please file an issue with the associated
project.
On some platforms, including Android, sdl3 tries to create the OpenGL context by itself even without creating
a renderer. This can manifest in errors like VK_ERROR_NATIVE_WINDOW_IN_USE_KHR when initializing Vulkan or GLES.
Add the following code before creating a window to fix the errors:
sdl3::hint::set("SDL_VIDEO_EXTERNAL_CONTEXT", "1")Rust, and sdl3-rs, are both still heavily in development, and you may run
into teething issues when using this. Before panicking, check that you're using
the latest version of both Rust and Cargo, check that you've updated sdl3-rs
to the latest version, and run cargo clean. If that fails, please let us know
on the issue tracker.
You can run the test suite via:
cargo test --features=test-mode
The test-mode feature allows running Sdl::new() from a thread other than the main thread, which is necessary for running the integration tests (test/*.rs).
We're looking for people to help get SDL3 support in Rust built, tested, and completed. You can help out!
If you see anything wrong, missing, or sub-optimal, please feel free to open a PR with your improvements.
If you would like to discuss ideas or ask questions, join the #rust channel on Discord.
- New features must be properly documented, be it via examples or inline documentation (via
cargo doc). Documentation must be for the end user as well as your next fellow contributor. - Breaking changes must have a proper argumentation with it. While the pre-1.0 state of this crate allows us to be somewhat unstable, useless breaking changes will be denied.
- Minor changes, breaking changes and new features added via Pull Request must be added in the changelog file. It is now mandatory to log your changes in the changelog. A short description with a link to your commit/pull request within GitHub is fine. Internal, documentation or meta-changes (travis build change, README instructions updates, ...) don't have to be added in the changelog.