Common types and structures used by wayland-client and wayland-server

39 releases

✓ Uses Rust 2018 edition

0.24.0 Sep 14, 2019
0.23.5 Jun 13, 2019
0.23.1 Mar 24, 2019
0.21.7 Nov 28, 2018
0.21.0-alpha1 Jul 18, 2018

#6 in GUI

Download history 4656/week @ 2019-06-01 5930/week @ 2019-06-08 7117/week @ 2019-06-15 6161/week @ 2019-06-22 6429/week @ 2019-06-29 6079/week @ 2019-07-06 4913/week @ 2019-07-13 5388/week @ 2019-07-20 5335/week @ 2019-07-27 5049/week @ 2019-08-03 5083/week @ 2019-08-10 5047/week @ 2019-08-17 5445/week @ 2019-08-24 5829/week @ 2019-08-31 5639/week @ 2019-09-07

23,909 downloads per month
Used in 223 crates (5 directly)

MIT license


crates.io Build Status codecov

Wayland rust crates

This project contains rust crates for using the wayland protocol, both client side and server side.

There are two ways to use them:

  • By default, they use a pure rust implementation of the protocol
  • If you set the use_system_lib cargo feature, they will rather act as bindings on top of the wayland system C libraries, and this will add methods to access pointers to the C objects in the API. You'll need to use this feature if you need to interact with a C library that requires wayland objects (typically to intialize an OpenGL context)

If you use the use_system_lib feature, the crates thus obviously require that the wayland C libs are installed on your system. You can however require that they are dynamically loaded at startup rather than directly linked by setting the dlopen flag. This can be useful if you want to ship a binary that should gracelly handle the absence of these libs (by fallbacking to X11 for example).

This repository actually hosts 8 crates. The 3 main crates you'll likely want to use:

  • wayland-client and wayland-server are the main crates for client and server side bindings
  • wayland-protocols regroups bindings on the official protocol extentions available

There are also two auxilliary crates:

  • wayland-egl, which is necessary client-side for OpenGL integration
  • wayland-cursor, which helps with loading cursor images from the system temes for use in your apps

And finally 3 internal crates, that you'll need only for integrating a custom protocol extension:

  • wayland-commons contains the protocol logic that can be shared between client-side and server-side
  • wayland-sys is the actual C bindings, on which the crates are built
  • wayland-scanner is the crate used to convert the XML protocol specifications into rust code


The documentation for the master branch is available online.

The documentation for the releases can be found on docs.rs:


Requires at least rust 1.33 to be used, and version 1.15 of the wayland system libraries if using the use_system_lib cargo feature.


~20K SLoC