Summary: | [GTK] Do not enable VIDEO_TRACK if VIDEO is disabled | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Alberto Garcia <berto> | ||||
Component: | Tools / Tests | Assignee: | Alberto Garcia <berto> | ||||
Status: | RESOLVED INVALID | ||||||
Severity: | Normal | CC: | cgarcia, commit-queue, dbates, mrobinson | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Attachments: |
|
Description
Alberto Garcia
2013-09-12 14:28:35 PDT
Created attachment 211476 [details]
Patch
Here's the patch. It makes VIDEO_TRACK follow VIDEO.
Of course it's also possible to have a flag to configure them separately. Should we do that instead?
Comment on attachment 211476 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=211476&action=review > Tools/ChangeLog:9 > + Make VIDEO_TRACK configurable because it needs to be disabled if > + VIDEO is also disabled. Not sure I understand the change, since you say "because it needs to be disabled if VIDEO is also disabled," but it was always disabled before. What you are doing here is enabling VIDEO_TRACK for release builds if video is enabled. Perhaps you're really after some interaction with build-webkit? Comment on attachment 211476 [details]
Patch
Apologies for how confusing the interaction of build-webkit and configure is, but the features defined in SetupWebKitFeatures.m4 describe the setup for release builds. We do not want to enable video track yet for release builds, so this patch isn't really correct. Furthermore, WebKitFeatureOverrides.txt should override any value you use here, I'm not sure it works.
You're right, running build-webkit with --no-video-track is enough, for some reason I thought it was not working. Sorry for the noise! |