| commit | 0190367cea6f94fc0bff470cfbf9313d9ac0ce94 | [log] [tgz] |
|---|---|---|
| author | kjellander <kjellander@webrtc.org> | Wed Apr 27 15:56:50 2016 |
| committer | Commit bot <commit-bot@chromium.org> | Wed Apr 27 15:56:56 2016 |
| tree | a8abc7194ca29b2846a6e7ba7757665d425150e7 | |
| parent | 6353723b029de581b1d0393ddf49c79f34b8f37c [diff] |
Revert of Delete video_render module. (patchset #12 id:220001 of https://codereview.webrtc.org/1912143002/ ) Reason for revert: This breaks every buildbot in chromium.webrtc.fyi and I don't see any roll in progress to address this (and I don't see how that would be possible either). Usage in Chrome: https://code.google.com/p/chromium/codesearch#search/&q=modules.gyp%3Avideo_render&sq=package:chromium&type=cs Example failures: https://build.chromium.org/p/chromium.webrtc.fyi/builders/Linux%20Builder/builds/5420 https://build.chromium.org/p/chromium.webrtc.fyi/builders/Win%20Builder/builds/4526 I think it's fine to delete our video_render_module_internal_impl target and those files, but video_render target needs to remain. Original issue's description: > Delete video_render module. > > BUG=webrtc:5817 > > Committed: https://crrev.com/97cfd1ec05d07ef233356e57f7aa4b028b74ffba > Cr-Commit-Position: refs/heads/master@{#12526} TBR=mflodman@webrtc.org,pbos@webrtc.org,nisse@webrtc.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=webrtc:5817 Review-Url: https://codereview.webrtc.org/1923613003 Cr-Commit-Position: refs/heads/master@{#12534}
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.
