[Webkit-unassigned] [Bug 144561] [GTK] Re-enable Quartz backend on cmake build system

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=144561

--- Comment #29 from Michael Catanzaro <mcatanzaro at igalia.com> ---
Well it would be lovely to support OS X if possible. Even lovelier to have an EWS bot so that we can catch commits that break GTK+ on OS X, as otherwise it's doomed to be constantly broken. But the only potential blocker (we haven't agreed yet) is this:

> A few questions though; excuse my technical ignorance, but is accelerated
> compositing being done outside of GDK? 

Yes, it's implemented in WebKit. Our concern is best summarized by the comment [1]: "we are going to be removing the non-OpenGL version of the texture mapper." Judging by your patch in [1], that's going to break OS X.

[1] https://bugs.webkit.org/show_bug.cgi?id=138332#c26

> Will it also not be supported on OSX with the X11 GDK backend?

I am not sure, maybe Martin or Zan would know, but I suspect it would. Basically, you want to go the opposite route than you did with bug #138332, and compile with EGL and the GL texture mapper. I don't know how hard that would be.

> If done outside of GDK, will you have to write
> separate implementations for X11 and Wayland?

Yes. There are already patches for the Wayland support (see bug #115803), but the patches are languishing in Bugzilla. (It's also broken with XWayland, which is really bad for Fedora 23.)

P.S. The most important reason to update your app to WebKit2 is to get security updates.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20150622/57006353/attachment.html>