commit | 98e153101276c7ca341082ca7bf4b10a9e23f2fc | [log] [tgz] |
---|---|---|
author | kjellander <kjellander@webrtc.org> | Sat Mar 04 23:08:44 2017 |
committer | Commit bot <commit-bot@chromium.org> | Sat Mar 04 23:08:44 2017 |
tree | a2df0dadca140cd202dd17cbf942696e36ef217c | |
parent | 991f8294cfdefc4295c1b4839d989d3043f41d94 [diff] |
Revert of Enable GN check for webrtc/{ortc,p2p} (patchset #4 id:60001 of https://codereview.webrtc.org/2714263004/ ) Reason for revert: Fails compile in Chromium for NaCl: https://build.chromium.org/p/chromium.webrtc.fyi/builders/Win%20Builder/builds/9320/ http://build.chromium.org/p/chromium.webrtc.fyi/builders/Mac%20Builder/builds/22215 http://build.chromium.org/p/chromium.webrtc.fyi/builders/Linux%20Builder/builds/14501 Original issue's description: > Enable GN check for webrtc/{ortc,p2p} > > Introduce new target //webrtc/p2p:rtc_p2p_test_utils to host > test-related utilities. > Previously uncovered header "base/fakecandidatepair.h" is now also in a target. > > BUG=webrtc:6828 > > Review-Url: https://codereview.webrtc.org/2714263004 > Cr-Commit-Position: refs/heads/master@{#17036} > Committed: https://chromium.googlesource.com/external/webrtc/+/c9515b6ce642875c4994deb25a5bb0132a958848 TBR=deadbeef@webrtc.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=webrtc:6828 Review-Url: https://codereview.webrtc.org/2735583002 Cr-Commit-Position: refs/heads/master@{#17038}
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.