Wayland 1.18 Alpha Released With Meson Support, Connection Sharing

[phoronix]

Phoronix: Wayland 1.18 Alpha Released With Meson Support, Connection Sharing

In meeting the plans for releasing Wayland 1.18 in February, the alpha release of this Wayland update is now available...

http://www.phoronix.com/scan.php?pag...Alpha-Released

[CommunityMember]

Meson or bust.

While I am sure there are strong opinions about which build system is better, almost anything seems better than base autotools at this point, and as Gnome and Weston have already moved to meson, it is the logical choice for that community.

[tildearrow]

Meson or bust.

Or CMake.

[uid313]

But no support for Vulkan, and no code in Rust.

[lu_tze]

But no support for Vulkan, and no code in Rust.

Wayland shouldn't have any GPU API-specific APIs. In case of Vulkan, it is Vulkan that has WSI (window system integration) layer on it's side of the fence. For Wayland, in the form of VK_KHR_wayland_surface.

[ascent12]

But no support for Vulkan, and no code in Rust.

This is talking about libwayland, the library which handles the low level wire protocol. It actually has nothing to do with graphics.
Vulkan clients have always worked, and Vulkan support in Wayland compositors are entirely a compositor issue, and has nothing to do with Wayland itself.

Why on earth would a C library suddenly stop wanting to be a C library? It's written in C for a very good reason, and just rewriting code for literally no reason is just an opportunity to introduce new bugs.

[theriddick]

Well this all sounds nice, shame NVIDIA is still not working well with Wayland, but if AMD releases that super GPU big navi and its not a flop, I won't need to worry about that for long

[uid313]

This is talking about libwayland, the library which handles the low level wire protocol. It actually has nothing to do with graphics.
Vulkan clients have always worked, and Vulkan support in Wayland compositors are entirely a compositor issue, and has nothing to do with Wayland itself.

Why on earth would a C library suddenly stop wanting to be a C library? It's written in C for a very good reason, and just rewriting code for literally no reason is just an opportunity to introduce new bugs.

But does Weston or GNOME Shell support Vulkan?
Yeah, maybe the low level library should be in C because it has bindings for many languages, but maybe the compositors ought to be written in Rust.

[Britoid]

But does Weston or GNOME Shell support Vulkan?
Yeah, maybe the low level library should be in C because it has bindings for many languages, but maybe the compositors ought to be written in Rust.

GNOME Shell does not support using Vulkan as a renderer, GTK4 does though so if GNOME Shell does get rewritten in GTK4 it could use it.

Rewriting the compositors in Rust would bring very little (if any) gain for an extreme amount of work, just because something is written in Rust doesn't make it better. C is perfectly fine for a compositor.

[uid313]

Rewriting the compositors in Rust would bring very little (if any) gain for an extreme amount of work, just because something is written in Rust doesn't make it better. C is perfectly fine for a compositor.

I just don't want my compositor to crash because unlike X.Org Server where when the compositor or window manager crashed it would just gracefully restart with all applications intact, when a Wayland compositor crashes everything goes down. I think.