wayland-sys
| Crates.io | wayland-sys |
| lib.rs | wayland-sys |
| version | 0.31.5 |
| source | src |
| created_at | 2015-10-03 11:08:21.431559 |
| updated_at | 2024-09-04 19:24:54.170754 |
| description | FFI bindings to the various libwayland-*.so libraries. You should only need this crate if you are working on custom wayland protocol extensions. Look at the crate wayland-client for usable bindings. |
| homepage | |
| repository | https://github.com/smithay/wayland-rs |
| max_upload_size | |
| id | 3150 |
| size | 35,076 |
Publishers (github:smithay:publishers)
documentation
https://docs.rs/wayland-sys/
README
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:
clientfor bindings tolibwayland-client.soserverfor bindings tolibwayland-server.socursorfor bindings tolibwayland-cursor.soeglfor bindings tolibwayland-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.