commit | b298f743b85cc7bfabc39cc4fdba2a7858a20d8b | [log] [tgz] |
---|---|---|
author | Sam Zackrisson <saza@webrtc.org> | Tue Oct 06 11:40:30 2020 |
committer | Commit Bot <commit-bot@chromium.org> | Tue Oct 06 11:40:43 2020 |
tree | 6b0ea40c7af352555bf74d5577c30b044e3ce4a5 | |
parent | fa2927970eb669536a79017ac68d1c6f670e4cff [diff] |
Revert "Replace sigslot usages with robocaller library." This reverts commit 40261c3663fe316cfe40262c59cee993165ccf63. Reason for revert: Breaks downstream project Original change's description: > Replace sigslot usages with robocaller library. > > - Replace all the top level signals from jsep_transport_controller. > - There are still sigslot usages in this file so keep the inheritance > and that is the reason for not having a binary size gain in this CL. > > Bug: webrtc:11943 > Change-Id: I249d3b9710783aef70ba273e082ceeafe3056898 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/185540 > Commit-Queue: Lahiru Ginnaliya Gamathige <glahiru@webrtc.org> > Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> > Reviewed-by: Karl Wiberg <kwiberg@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#32321} TBR=mbonadei@webrtc.org,kwiberg@webrtc.org,glahiru@webrtc.org Change-Id: Icf438f87c3d95940d858db3cc5848b23abb82fc4 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: webrtc:11943 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/186844 Reviewed-by: Sam Zackrisson <saza@webrtc.org> Commit-Queue: Sam Zackrisson <saza@webrtc.org> Cr-Commit-Position: refs/heads/master@{#32324}
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.
See here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.