| Crates.io | wayland-server |
| lib.rs | wayland-server |
| version | 0.31.10 |
| created_at | 2016-09-27 16:35:21.136013+00 |
| updated_at | 2025-07-28 22:55:30.108806+00 |
| description | Bindings to the standard C implementation of the wayland protocol, server side. |
| homepage | |
| repository | https://github.com/smithay/wayland-rs |
| max_upload_size | |
| id | 6643 |
| size | 225,569 |
Server side API for the Wayland protocol. This crate provides infrastructure for manipulating
Wayland objects, as well as object definitions for the core Wayland protocol. Protocol extensions
can be supported as well by combining this crate with wayland-protocols, which provides object
definitions for a large set of extensions.
Note: This crate is a low-level interface to the Wayland protocol. If you are looking for a more battery-included toolkit for writing a Wayland server, you may consider Smithay, which is a Wayland server framework built on top of it.
The crate has different backends to Wayland protocol serialization:
unsafe code.use_system_lib makes it instead bind to the system libwayland-server.so. This
allows you to access C pointer versions of the wayland objects, which is necessary for interfacing
with other non-Rust Wayland-related libraries (such as for OpenGL support, see the wayland-egl crate).dlopen implies use_system_lib, but additionaly the crate will not explicitly
link to libwayland-server.so and instead try to open it at runtime, and return an error if it cannot
find it. This allows you to build apps that can gracefully run in non-Wayland environment without needing
compile-time switches.