commit | 2a959d96c9046c8dc49225c9ddd2aa58e7468acf | [log] [tgz] |
---|---|---|
author | Sam Zackrisson <saza@webrtc.org> | Mon Jul 23 14:48:07 2018 +0000 |
committer | Commit Bot <commit-bot@chromium.org> | Mon Jul 23 14:48:17 2018 +0000 |
tree | e72d5f284b7f546f330424b7b476c0f934526a83 | |
parent | 771b50ca0b92477ce8aabba025e959790dd1a949 [diff] |
Revert "Add one-stop-shop for built-in AEC toggling in APM" This reverts commit 771b50ca0b92477ce8aabba025e959790dd1a949. Reason for revert: Introduces error-prone config. Original change's description: > Add one-stop-shop for built-in AEC toggling in APM > > This does not change what AEC functionality is available. > However, a client that only uses this interface - and not the submodule > pointer accessors - gets simpler code, and is guaranteed not to run any > two AECs in tandem. > > The submodule interface EchoControlMobile is being deprecated in > https://webrtc-review.googlesource.com/c/src/+/89392 > > Bug: webrtc:9535 > Change-Id: Id9326074e566be6d8768010fc421c457beff402c > Reviewed-on: https://webrtc-review.googlesource.com/89386 > Commit-Queue: Sam Zackrisson <saza@webrtc.org> > Reviewed-by: Per Ã…hgren <peah@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#24066} TBR=saza@webrtc.org,peah@webrtc.org Change-Id: I43283a1b22538a4caa77313499989146b2ce67f1 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: webrtc:9535 Reviewed-on: https://webrtc-review.googlesource.com/90060 Reviewed-by: Sam Zackrisson <saza@webrtc.org> Commit-Queue: Sam Zackrisson <saza@webrtc.org> Cr-Commit-Position: refs/heads/master@{#24067}
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 http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.