commit | c09525a547ec1688fcd023ffc13a95115c63f884 | [log] [tgz] |
---|---|---|
author | hbos <hbos@webrtc.org> | Fri Feb 05 19:02:42 2016 |
committer | Commit bot <commit-bot@chromium.org> | Fri Feb 05 19:02:47 2016 |
tree | b4357011ee9fb4e218bd7e91bdd28fdf9ae8492d | |
parent | 50fca62809c858686d533d93cd937d41e4791e5f [diff] |
Revert of Default build flag |rtc_use_h264| to |proprietary_codecs| if not on Android/iOS. (patchset #1 id:1 of https://codereview.webrtc.org/1660403004/ ) Reason for revert: Trybots red? Don't have time to intvestigate Original issue's description: > Default build flag |rtc_use_h264| to |proprietary_codecs| > if not on Android/iOS. > > This means proprietary_codecs=1 && ffmpeg_branding=Chrome > can be used to enable this H.264 enc/dec implementation > instead of rtc_use_h264=1 && ffmpeg_branding=Chrome. > This is used by both Chromium trybots (but not default > Chromium build) and offical Chrome build, meaning we will > be able to test and enable H.264 in chromium. > > This change would otherwise be enough to launch this > feature in Chrome, but because we do not want to do that > before we have chromium browser tests and are ready to flip > the switch, this CL prevents chromium from using H.264 just > yet: https://codereview.chromium.org/1641163002/ (landing > this after that CL). > > BUG=chromium:500605, chromium:468365 > > Committed: https://crrev.com/7cd94f66ebfe5bf808d7dcb8da069d35f4a2b31a > Cr-Commit-Position: refs/heads/master@{#11506} TBR=kjellander@webrtc.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=chromium:500605, chromium:468365 Review URL: https://codereview.webrtc.org/1677623002 Cr-Commit-Position: refs/heads/master@{#11508}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others. This page is maintained by the Google Chrome team.
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.