Hi all I'm working on a new build system called Meson. As part of development I take open source projects and rewrite their build systems to ensure it fulfils real world requirement. This time I took Wayland and Weston.
The patches are attached to this message for anyone to try them out. They apply against git trunk and are compiled with the following steps. First Wayland: mkdir build; cd build PKG_CONFIG_PATH=... meson --prefix=/your/install/root ninja [ninja test] ninja install Then do Weston: mkdir build; cd build PKG_CONFIG_PATH=... PATH=... LD_LIBRARY_PATH=.. meson .. ninja [ninja test] Wayland compiles and installs fully apart from Doxygen. Weston builds only choice bits, the basic library, some demo clients and some unit tests. Performance-wise the configuration step takes about 13 seconds for both when using Autotools and less than a second for Meson. Compilation times are roughly the same. Autotools build definitions are 21 kilobytes for Wayland and 54 kilobytes for Weston. Meson takes 10k and 20k, respectively. (Though note that they do not do everything that the autotools-ones do.) For more information, just go to the github project page: https://github.com/jpakkane/meson The presentation "Making build systems not suck" from LCA2015 is a good overview of Meson: https://www.youtube.com/watch?v=KPi0AuVpxLI That's about it. I hope you find it interesting,
wayland-meson.patch
Description: Binary data
weston-meson.patch
Description: Binary data
_______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel
