commit | a81f6a3fc05378faa0e944c6c13d9beece2dac94 | [log] [tgz] |
---|---|---|
author | hbos <hbos@webrtc.org> | Sun Feb 07 23:05:22 2016 |
committer | Commit bot <commit-bot@chromium.org> | Sun Feb 07 23:05:26 2016 |
tree | 0ee7c7b8be453ccc5969e67d00d846c9030f77ff | |
parent | 10b9dd7ab1a8c3f80b2d2924be658e43131a4fbe [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/1674103002/ ) Reason for revert: Chromium FYI turns red. 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). > > Note: This is a re-land of > https://codereview.webrtc.org/1660403004/. Reverting it > was not necessary. > > TBR=kjellander@webrtc.org > BUG=chromium:500605, chromium:468365 > > Committed: https://crrev.com/10b9dd7ab1a8c3f80b2d2924be658e43131a4fbe > Cr-Commit-Position: refs/heads/master@{#11517} 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/1675113002 Cr-Commit-Position: refs/heads/master@{#11518}
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.