[chromium] Put webkit compositor binding files in separate conditionally included gyp section
Created attachment 159224 [details] Patch
We unconditionally pull 'webkit/' from the chromium repo, so a separate DEPS entry isn't needed for webkit/compositor/
Comment on attachment 159224 [details] Patch Attachment 159224 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/13514999
Comment on attachment 159224 [details] Patch Attachment 159224 [details] did not pass cr-android-ews (chromium-android): Output: http://queues.webkit.org/results/13533071
Hmm, I thought that gyp var would have been picked up from WebCore.gypi. Interesting....
Created attachment 159239 [details] Patch
Duh, I default-initialized the variable in WebCore.gyp. This inits it as well in WebKit.gyp - I'm not sure if that is the more idomatic thing or if I should set it in WebCore.gypi. Advantage of the latter is I'll only have to flip the default in one place when it comes to that, but the disadvantage is it'll "leak" to a bunch more places. What's the standard practice here?
Comment on attachment 159239 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=159239&action=review dunno what the "standard practice" is ... > Source/WebKit/chromium/WebKit.gyp:841 > + 'webkit_compositor_bindings_files', think this needs to be <@(webkit_compositor_bindings_files)
Created attachment 159249 [details] Patch
Comment on attachment 159249 [details] Patch Clearing flags on attachment: 159249 Committed r125994: <http://trac.webkit.org/changeset/125994>
All reviewed patches have been landed. Closing bug.