Wayland's Weston Continues Going Through Refactoring
For those of you not paying attention to Weston Git or the mailing lists, this reference Weston compositor has been going through a period of refactoring.
The actual Weston compositor source code is now coded in compositor/ while the other code is in libweston. This is for cleaning up the code and part of the broader effort of formalizing Libweston.
The intention of libweston is making it easier to write a full-featured Wayland compositor. Libweston implements most of the basic Wayland protocol bits and other shared fundamentals to Wayland compositors to make it easy for bringing up new compositors.
This Libweston work has been discussed on the mailing lists for months while in June is when much of the code began to appear in Git, including the libweston library. The Libweston support will be present in the Wayland/Weston 1.12 release later this year.
The actual Weston compositor source code is now coded in compositor/ while the other code is in libweston. This is for cleaning up the code and part of the broader effort of formalizing Libweston.
The intention of libweston is making it easier to write a full-featured Wayland compositor. Libweston implements most of the basic Wayland protocol bits and other shared fundamentals to Wayland compositors to make it easy for bringing up new compositors.
This Libweston work has been discussed on the mailing lists for months while in June is when much of the code began to appear in Git, including the libweston library. The Libweston support will be present in the Wayland/Weston 1.12 release later this year.
Add A Comment