21cddffd99
This CL consistently use: * relative paths for WebRTC dependent targets (test_support) * absolute paths for shared dependent targets (abseil) This is a necessary (but insufficient) step to build WebRTC tests from Chromium tree (rtc_include_tests=true), since test/ doesn't sit anymore in the top level directory. We also make sure that target declarations and uses are consistent in regard to build_with_chromium flag. Bug: webrtc:9943 Bug: webrtc:9855 Change-Id: I21dea98894df2fd4bfe2fd7ee7b71ba971e0ab5b Reviewed-on: https://webrtc-review.googlesource.com/c/108720 Reviewed-by: Patrik Höglund <phoglund@webrtc.org> Commit-Queue: Yves Gerey <yvesg@webrtc.org> Cr-Commit-Position: refs/heads/master@{#25445}
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