| commit | 9acf1c1f549791b39ad7b2d0d472c41d0f2cd4b2 | [log] [tgz] |
|---|---|---|
| author | Mirko Bonadei <mbonadei@webrtc.org> | Fri Oct 19 17:17:34 2018 +0200 |
| committer | Commit Bot <commit-bot@chromium.org> | Mon Oct 22 07:25:32 2018 +0000 |
| tree | 4154990ae6c25d0e10c8e752ddf73383de5e1a96 | |
| parent | 648d28ad62573c7b1a1e5b05a6122227f7272950 [diff] |
Reland "Make sure Chromium will pick the correct field_trial/metric impl." This is a reland of 8dc280d804bc49932f429955b27ff385054ddfa0 Original change's description: > Make sure Chromium will pick the correct field_trial/metric impl. > > 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} Bug: webrtc:9631 Change-Id: I9b6e6f3f91881e8e3fa8bc6e97f797e8b7e4e4ca Reviewed-on: https://webrtc-review.googlesource.com/c/107163 Reviewed-by: Karl Wiberg <kwiberg@webrtc.org> Commit-Queue: Mirko Bonadei <mbonadei@webrtc.org> Cr-Commit-Position: refs/heads/master@{#25281}
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.