I'm going to say no to this because:
* Well-written code doesn't need Cairo to use GL to get the best
performance. Just don't re-render Cairo parts on important code paths.
* Even if there were no known bugs in the GL backend, it would still
pose an unnecessary risk to the stability of mature c
I remember talking to the GNOME developers about this, I think it was in
person at a conference last year. From what I recall, they said the
OpenGL backend had issues so there was good reason to leave it disabled.
I don't know if it's the same reason as in comment #5, but it probably
doesn't matter
Here is a link for cairo/egl: https://jan.newmarch.name/Wayland/Cairo/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1977748
Title:
Build Cairo with OpenGL support
Status
I was looking to run cairo on wayland. A web search led me to the EGL
device. I'm guessing by buffer you mean IMAGE surface (after digging in
the headers a bit). I am happy to try that. But I'm guessing at some
point in the future peeps will want it. Thanks for digging in.
--
You received
I always assumed Cairo was for software rendering only. That's how
gnome-shell and others use it -- render to a software buffer and then
upload that to a GL texture.
I guess the advantage of building Cairo with native GL support is that
it all happens on the GPU with less CPU time wasted... Althou
The openGL option was disabled a long time ago in Debian, the rational isn't
really descriptive on the issue though
https://salsa.debian.org/gnome-team/cairo/-/commit/a4bad9f84
But we also disabled it around the time in Ubuntu due to bug #725434
with nvidia drivers, but comments from 2015 suggest
6 matches
Mail list logo
