Reason for revert: This is preventing a WebRTC roll into Chromium. See https://codereview.chromium.org/1877263003/ Original issue's description: > Fix screen capturers to initialize on the same thread on which Start() is called. > > Previously screen capturers were initialized when they are created. > This means that in the CRD host they were initialized on the thread > that's different from the thread on which they are used. Because of this > on Linux the host was using XErrorTrap() on two different threads and > this is not supported. Now ScreenCapturer implementations always > initialize themselves on the thread on which Start() is called. > > Also added ThreadChecker to make sure the capturers are always called > from the same thread. > > BUG=600432 > > Committed: https://crrev.com/e8d4b7d8a3d298438a2ebd9ee8d5aa71f42cf033 > Cr-Commit-Position: refs/heads/master@{#12285} TBR=jamiewalch@chromium.org,sergeyu@chromium.org # Not skipping CQ checks because original CL landed more than 1 days ago. BUG=600432 Review URL: https://codereview.webrtc.org/1882083002 Cr-Commit-Position: refs/heads/master@{#12334}
Revert of CQ: Remove libfuzzer trybot from default trybot set. (patchset #1 id:1 of https://codereview.webrtc.org/1764093002/ )
Revert of Added webrtc/base/safe_conversions.h as a pseudonym (patchset #1 id:20001 of https://codereview.webrtc.org/1774933003/ )
Revert of Fix screen capturers to initialize on the same thread on which Start() is called. (patchset #3 id:80001 of https://codereview.webrtc.org/1861893002/ )
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.
Development
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://chromium.googlesource.com/external/webrtc
- Samples and reference apps: https://github.com/webrtc
- Mailing list: http://groups.google.com/group/discuss-webrtc
- Continuous build: http://build.chromium.org/p/client.webrtc
Description
The idea is to make CMake build for WebRTC m130 version - for audio processing module
Languages
C++
90.3%
Java
2.9%
C
2.2%
Objective-C++
2%
Python
1.3%
Other
1%