8dc280d804
Chromium wants to pick its own field_trial and metrics implementation, and WebRTC has an escape hatch to let it remove the definition of these symbols. This obviously causes liker errors if Chromium will not pick the correct dependency (which cannot be forced by GN check since there is no header inclusion). Instead of hoping that the build target with the correct implementation will be added as a dependency somewhere in the build graph, this CL wants to explicitly add the dependency as close as possible to the headers, so if they are included and WebRTC is built as part of Chromium the correct implementation will be linked into the binary. Bug: webrtc:9631 Change-Id: I2d1cfe541726341adfdf81e14e036464aa003d4d Reviewed-on: https://webrtc-review.googlesource.com/c/107040 Reviewed-by: Karl Wiberg <kwiberg@webrtc.org> Commit-Queue: Mirko Bonadei <mbonadei@webrtc.org> Cr-Commit-Position: refs/heads/master@{#25269}
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.
Development
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.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://webrtc.googlesource.com/src
- 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
- Coding style guide
- Code of conduct