[][src]Crate wayland_scanner

Wayland scanner crate

This crate is a rust equivalent of the wayland-scanner tool from the official wayland C library.

You can use in your build script to generate the rust code for any wayland protocol file, to use alongside the wayland_client and wayland_server crate to build your applications.

How to use this crate

This crate is to be used in a build script. It provides you two functions, generate_c_code and generate_c_interfaces. They'll allow you to generate the code to use with the wayland_client or wayland_server crates for any XML wayland protocol file (NB: you don't need to do it for the core protocol, which is already included in both crates).

First, have the XML files you want to use in your project, somewhere the build script will be able to read them.

Then, you'll need to invoke both generate_c_interfaces and generate_c_code for each of these files.

A sample build script:

extern crate wayland_scanner;

use std::env::var;
use std::path::Path;

use wayland_scanner::{Side, generate_c_code, generate_c_interfaces};

fn main() {
    // Location of the xml file, relative to the `Cargo.toml`
    let protocol_file = "./my_protocol.xml";

    // Target directory for the generate files
    let out_dir_str = var("OUT_DIR").unwrap();
    let out_dir = Path::new(&out_dir_str);

        Side::Client, // Replace by `Side::Server` for server-side code

    // interfaces are the same for client and server

The above example will output two .rs files in the OUT_DIR defined by cargo. Then, you'll need to include these two generated files (using the macro of the same name) to make this code available in your crate.

This example is not tested
// The generated code will import stuff from wayland_sys
extern crate wayland_sys;
extern crate wayland_client;

// Re-export only the actual code, and then only use this re-export
// The `generated` module below is just some boilerplate to properly isolate stuff
// and avoid exposing internal details.
// You can use all the types from my_protocol as if they went from `wayland_client::protocol`.
pub use generated::client as my_protocol;

mod generated {
    // The generated code tends to trigger a lot of warnings
    // so we isolate it into a very permissive module

    pub mod interfaces {
        // include the interfaces, they just need to be accessible to the generated code
        // so this module is `pub` so that it can be imported by the other one.
        include!(concat!(env!("OUT_DIR"), "/my_protocol_interfaces.rs"));

    pub mod client {
        // If you protocol interacts with objects from other protocols, you'll need to import
        // their modules, like so:
        pub(crate) use wayland_client::protocol::{wl_surface, wl_region};
        include!(concat!(env!("OUT_DIR"), "/my_protocol_code.rs"));



Side to generate



Generate the code for a protocol using the C system libs


Generate the code for a protocol from/to IO streams using the C system libs


Generate the interfaces for a protocol


Generate the interfaces for a protocol from/to IO streams


Generate the code for a protocol using the Rust implementation


Generate the code for a protocol from/to IO streams using the rust implementation