[Webkit-unassigned] [Bug 95854] [Chromium] Compositor build errors prevent rolling Chromium into WebKit

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Sep 5 09:47:21 PDT 2012


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





--- Comment #7 from James Robinson <jamesr at chromium.org>  2012-09-05 09:47:35 PST ---
(In reply to comment #0)
> - There are two compositors, one in Chromium's cc/ directory, one in WebKit. The gyp "use_libcc_for_compositor" variable toggles this: 0 means WebKit, 1 means cc/.

Yes (technically they're copies of each other, we're moving the WebKit one into cc/)

> - Chromium and WebKit currently both build with use_libcc_for_compositor=0. Are there bots which have use_libcc_for_compositor=1? Is there a bug or issue I can track for progress on this?

There's no bot.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list