q3k
/
abrasion
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
abrasion/third_party/cargo/vendor/wayland-sys-0.28.5
History
q3k 4a50bbf00d third_party/cargo: re-raze, fix winapi for windows 2021-05-03 23:43:36 +02:00
..
src 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-sys

This crate provides raw bindings to the system libwayland-*.so libraries. If you are looking for a Rust API over the Wayland protocol, see the wayland-client or wayland-server crates instead.

Bindings to the different libraries are enabled by the different cargo features:

  • client for bindings to libwayland-client.so
  • server for bindings to libwayland-server.so
  • cursor for bindings to libwayland-cursor.so
  • egl for bindings to libwayland-egl.so

Furthermore, the dlopen cargo feature will switch the library to a mode where, instead of directly linking to these system libraries, it'll instead try to open them at runtime. This allows to create binaries that can gracefully handle being run on non-Wayland environments. In that case the crate should be used with its provided ffi_dispatch!() macro, to support both modes seamlessly.