On Tue, 8 May 2018 13:49:14 -0700 Matt Turner <[email protected]> wrote:
> On Mon, Apr 9, 2018 at 10:57 AM, Derek Foreman <[email protected]> wrote: > > Wayland 1.15.0 is now out. > > > > Some highlights: > > Compositor writers take note - wl_subcompositor.get_subsurface is now > > documented to be double buffered. It wasn't clearly specified to be so > > before (this change should be non breaking in practice and merely remove > > the opportunity for a render glitch in the compositor.) > > > > New API, wl_display_destroy_clients() has been added to help some > > compositors clean up clients before destroying their display. > > > > wayland-scanner can now generate either public or private symbols, and > > the old command line option "code" will emit a warning. It also has a > > new --strict option to immediately exit on DTD validation failure. > > > > libwayland-egl is now part of libwayland, and will presumably be removed > > from mesa in the not too distant future. > > Since there doesn't seem to have been any announcement or guidance on > the Mesa side for what distros are supposed to do, I'll ask here: > > Are distros supposed to stop passing "wayland" to Mesa's > --with-platforms= configure option? Very much not, as that would remove all Wayland support, not just libwayland-egl. The main piece of Wayland support implementation is still in Mesa even after libwayland-egl gets removed from there. Emil, any further advice for distributors how to handle the transition? Thanks, pq
pgpgsInefs43j.pgp
Description: OpenPGP digital signature
_______________________________________________ wayland-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/wayland-devel
