commit | 8644f2b7632cff5e46560c2f5cf7c0dc071aa32d | [log] [tgz] |
---|---|---|
author | Mirko Bonadei <mbonadei@webrtc.org> | Sat Feb 13 10:17:40 2021 |
committer | Commit Bot <commit-bot@chromium.org> | Sat Feb 13 16:16:35 2021 |
tree | 60e75c37fde6e6dd9da95368bb58f9d354f32e0d | |
parent | 130ff4974b8ef840c30be8c04d6da4a5a942cd4b [diff] |
Revert "Split peer_connection_integrationtest.cc into pieces" This reverts commit cae4656d4a7439e25160ff4d94e50949ff87cebe. Reason for revert: Breaks downstream build (missing INSTANTIATE_TEST_SUITE_P in pc/data_channel_integrationtest.cc). Original change's description: > Split peer_connection_integrationtest.cc into pieces > > This creates two integration tests: One for datachannel, the other > for every test that is not datachannel. > > It separates out the common framework to a new file in pc/test. > Also applies some fixes to IWYU. > > Bug: None > Change-Id: I919def1c360ffce205c20bec2d864aad9b179c3a > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/207060 > Reviewed-by: Henrik Boström <hbos@webrtc.org> > Commit-Queue: Harald Alvestrand <hta@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#33244} TBR=hbos@webrtc.org,hta@webrtc.org # Not skipping CQ checks because original CL landed > 1 day ago. No-Try: True Bug: None Change-Id: I7dbedd3256cb7ff47eb5f8cd46c7c044ed0aa1e0 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/207283 Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> Commit-Queue: Mirko Bonadei <mbonadei@webrtc.org> Cr-Commit-Position: refs/heads/master@{#33255}
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 here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.