abrasion/third_party/cargo/vendor/wayland-protocols-0.28.5
q3k 4a50bbf00d third_party/cargo: re-raze, fix winapi for windows 2021-05-03 23:43:36 +02:00
..
misc third_party/cargo: update 2021-04-03 16:13:10 +00:00
protocols third_party/cargo: update 2021-04-03 16:13:10 +00:00
src third_party/cargo: update 2021-04-03 16:13:10 +00:00
wlr-protocols third_party/cargo: update 2021-04-03 16:13:10 +00:00
.cargo-checksum.json third_party/cargo: update 2021-04-03 16:13:10 +00:00
BUILD.bazel third_party/cargo: re-raze, fix winapi for windows 2021-05-03 23:43:36 +02:00
Cargo.toml third_party/cargo: update 2021-04-03 16:13:10 +00:00
LICENSE.txt third_party/cargo: update 2021-04-03 16:13:10 +00:00
README.md third_party/cargo: update 2021-04-03 16:13:10 +00:00
build.rs third_party/cargo: update 2021-04-03 16:13:10 +00:00

README.md

crates.io docs.rs Continuous Integration codecov

wayland-protocols

This crate provides Wayland object definitions for many of the Wayland protocol extensions available. It is meant to be used in addition to wayland-client or wayland-server.

This crate provides bindings for the following protocols extensions:

The provided objects are controlled by cargo features:

  • the client and server cargo features respectively enable the generation of client-side and server-side objects
  • the unstable_protocols enable the generation of not-yet-stabilized protocols

If you wish for other protocols to be integrated, please open an issue on Github. Only protocols that are meant to be stabilized and largely used are in scope of this crate. If you wish to generate bindings for your own internal protocol, you can directly use wayland-scanner.