2f28370e65
We needed a hack in test_main_lib.cc to ensure fileutils were always linked with test binaries downstream. When I removed the hack, it broke the binaries that were _not_ using fileutils because a certain bazel rule expects to be able to pass the flag to all test binaries. The solution is to move the flag to test_main_lib.cc. This is the right place for it since it's apparently in the contract of a WebRTC test binary to support this flag. We then have to pass the value down to the override, which is why I add a new function for that. I leave the flag unimplemented in OSS because no one is using it here anyway. It will be implemented downstream. Bug: webrtc:9792 Change-Id: I21b3deb43bf0cd56d6aa2622dc5519370a0307a9 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/156568 Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> Commit-Queue: Patrik Höglund <phoglund@webrtc.org> Cr-Commit-Position: refs/heads/master@{#29474}
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