This is the first of (many) parts in the upstreaming of the Wayland driver for Wine. Since the amount of code and commits is large, my approach is to upstream the driver in multiple parts in a serial fashion, with each part being a cohesive (to the degree possible) set of not too many commits. When each part is reviewed and merged, I will move on to proposing the next part. My main goal with this approach is to make reviewing easier and more focused. If you have other ideas about how to improve this process for the reviewers, please let me know.

A lot of pieces need to fall into place before the driver becomes even remotely functional, so, some MRs (especially the initial ones) will be a bit more preparatory in nature. To aid in the understanding of and justification for some of the code introduced in such MRs, all the remaining driver commits are always going to be available at

Part 1

This MR introduces the Wayland driver PE and unixlib components with some basic code, and prepares the makedep tool to be able to handle Wayland protocol files. Please see the individual commit message for more details.

Some questions I would appreciate some feedback on in the context of this MR:

  1. Should the Wayland driver build be enabled by default at this point? (currently it’s explicitly opt-in with –with-wayland)
  2. How should the Wayland driver build be integrated with CI? (currently piggybacking on gitlab/build-linux by adding –with-wayland)

Note that building the Wayland driver should not affect running/testing on X11/Xwayland etc, since it’s placed lower in the driver priority list.

Part 2 preview: We will handle basic Wayland wl_output (i.e., display) events and populate the Wine monitor information.

Read More