I'm glad you could set up the environment in your machine :) Regarding
the one-line change you mentioned, we indeed are having a few issues
with the EGL headers and specifically the EGLNativeDisplayType type
definition. In particular, Chromium is getting the EGL definitions from
the wrong direc
Got the chorme-ozone working for ARM with proprietary GPU drivers. It is
neat!
WebGL also working very good.
I recommend to use gold linker and latest ninja(1.4).
I have to make only the following change
@@ -117,7 +117,7 @@ bool GLSurfaceEGL::InitializeOneOff() {
LOG(ERROR) << "OZONE failed
argh, Pekka (pq) just told me in #wayland that we're probably talking
about two different things here. Sorry, my confusion.
If you were mentioning about building an Gentoo package out of Chromium
Wayland, then no, I don't think anyone tried that yet. As mentioned in
the blog announcement messa
no, there isn't any automated compilation tool yet.
To be honest I'm not entirely sure whether it's worthing having such
tool. We basically have Ozone-Wayland repository to be cloned in which
pulls in all the remaining dependencies (well, not libwayland...) and
for that we'd need about half do
