#wayland #sys #server

wayland-sys

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.

100 releases

✓ Uses Rust 2018 edition

new 0.26.6 May 23, 2020
0.26.3 Apr 22, 2020
0.25.0 Feb 7, 2020
0.24.1 Dec 13, 2019
0.2.0 Nov 9, 2015
Download history 10578/week @ 2020-02-06 10545/week @ 2020-02-13 11402/week @ 2020-02-20 9489/week @ 2020-02-27 8395/week @ 2020-03-05 8624/week @ 2020-03-12 10382/week @ 2020-03-19 9731/week @ 2020-03-26 10082/week @ 2020-04-02 10433/week @ 2020-04-09 10765/week @ 2020-04-16 11351/week @ 2020-04-23 14433/week @ 2020-04-30 14747/week @ 2020-05-07 15289/week @ 2020-05-14 14539/week @ 2020-05-21

48,175 downloads per month
Used in 470 crates (17 directly)

MIT license

32KB
536 lines

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.

Dependencies

~39KB