Originally posted by timrichardson
View Post
Announcement
Collapse
No announcement yet.
Chromium's Ozone Wayland Back-End Is Now Considered Beta, Aiming To Ship Next Year
Collapse
X
-
Originally posted by carewolf View Post
Yes, but it is a different build of Chromium. You either build it for Ozone or for X11. You can theoretically use an Ozone X11 backend but it works poorly upstream.
Fork Chromium with Wayland backend support has been around for years.
Wayland implementation for Chromium Ozone classes. Contribute to intel/ozone-wayland development by creating an account on GitHub.
Milestone Santa Release Date: 27 Dec 2013. Based on Chromium- Version: 32.0.1700.69. Channel: Beta. Revision: 6f5eb8456ae3021c7396be3a67c454d82b2cfb30. New Features enabled in this release: WebGL....
It is now part of the Chromium project.
Comment
-
Originally posted by latalante View Post
Don't mix if you don't know something.
Fork Chromium with Wayland backend support has been around for years.
Wayland implementation for Chromium Ozone classes. Contribute to intel/ozone-wayland development by creating an account on GitHub.
https://github.com/intel/ozone-wayla...g/32.0.1700.69
It is now part of the Chromium project.
To eloborate. Chromium has traditionally had multiple backends that are selected at configure time before building. So you select X11, macOS or Windows, etc. They have tried to replace that with a backend that can be replaced at runtime called Ozone, so if you configure and built Chromium on Ozone, it can use multiple Ozone backends at runtime. Wayland has been implemented as an Ozone backend and thus requires an Ozone build of Chromium. Unfortunately the main builds of Chromium still use the direct X11 backend instead of Ozone with Ozone-X11 backend. The result of this is that an Ozone build works poorly with X11, so you have one binary with direct X11 usage, and one with Ozone usage that can support Wayland. And the default is the direct X11 using one.Last edited by carewolf; 05 December 2019, 08:53 AM.
- Likes 5
Comment
-
Originally posted by carewolf View PostDon't reply if you don't understand my comment. It exist, but is a separate build exactly as a I said. Separate build means separate binaries, instead of having everything work from a single binary.
To eloborate. Chromium has traditionally had multiple backends that are selected at configure time before building. So you select X11, macOS or Windows, etc. They have tried to replace that with a backend that can be replaced at runtime called Ozone, so if you configure and built Chromium on Ozone, it can use multiple Ozone backends at runtime. Wayland has been implemented as an Ozone backend and thus requires an Ozone build of Chromium. Unfortunately the main builds of Chromium still use the direct X11 backend instead of Ozone with Ozone-X11 backend. The result of this is that an Ozone build works poorly with X11, so you have one binary with direct X11 usage, and one with Ozone usage that can support Wayland. And the default is the direct X11 using one.
I am talking about chromium with support for native wayland and only about it.
Code:chromium --ozone-platform=wayland
Users choose Wayland consciously and they have limitations in mind. They are looking for fully native solutions.
I am not afraid to install a special version.
Comment
-
I'd really like to try this on Arch but unfortunately there are no [working] pre-built packages, even from the AUR. You need a pretty beefy computer to compile this. I attempted to do so with my old laptop with an i3 and 8GB of RAM, and after 2.5 hours it failed because I ran out of memory.
- Likes 2
Comment
-
Originally posted by carewolf View PostDon't reply if you don't understand my comment. It exist, but is a separate build exactly as a I said. Separate build means separate binaries, instead of having everything work from a single binary.
To eloborate. Chromium has traditionally had multiple backends that are selected at configure time before building. So you select X11, macOS or Windows, etc. They have tried to replace that with a backend that can be replaced at runtime called Ozone, so if you configure and built Chromium on Ozone, it can use multiple Ozone backends at runtime. Wayland has been implemented as an Ozone backend and thus requires an Ozone build of Chromium. Unfortunately the main builds of Chromium still use the direct X11 backend instead of Ozone with Ozone-X11 backend. The result of this is that an Ozone build works poorly with X11, so you have one binary with direct X11 usage, and one with Ozone usage that can support Wayland. And the default is the direct X11 using one.
Comment
Comment