#wayland

wayland-backend

Low-level bindings to the Wayland protocol

18 releases

0.1.0-beta.8 Jul 15, 2022
0.1.0-beta.7 Jul 4, 2022
0.1.0-beta.6 Jun 25, 2022
0.1.0-beta.3 May 27, 2022
0.1.0-alpha10 Apr 7, 2022

#316 in GUI

Download history 162/week @ 2022-04-22 305/week @ 2022-04-29 218/week @ 2022-05-06 346/week @ 2022-05-13 630/week @ 2022-05-20 670/week @ 2022-05-27 1050/week @ 2022-06-03 1209/week @ 2022-06-10 476/week @ 2022-06-17 427/week @ 2022-06-24 304/week @ 2022-07-01 327/week @ 2022-07-08 478/week @ 2022-07-15 437/week @ 2022-07-22 422/week @ 2022-07-29 524/week @ 2022-08-05

1,909 downloads per month
Used in 8 crates (4 directly)

MIT license

380KB
8K SLoC

crates.io docs.rs Continuous Integration codecov

wayland-backend

Backend API for wayland crates

This crate provide low-level APIs for interacting with the Wayland protocol, both client-side and server-side. For higher-level interfaces, see the wayland-client and wayland-server crates.

Two possible backends are provided by this crate: the system backend ([sys] module) which relies on the system-provided wayland libraries, and the rust backend ([rs] module) which is an alternative rust implementation of the protocol. The rust backend is always available, and the system backend is controlled by the client_system and server_system cargo features. The dlopen cargo feature ensures that the system wayland libraries are loaded dynamically at runtime, so that your executable does not link them and can gracefully handle their absence (for example by falling back to X11).

Additionnaly the default backends are reexported as toplevel client and server modules in this crate. For both client and server, the default backend is the system one if the associated cargo feature is enabled, and the rust one otherwise. Using these reexports is the recommended way to use the crate.

Both backends have the exact same API, except that the system backend additionnaly provides functions related to FFI.

Dependencies

~2MB
~35K SLoC