Revert "Introduce rtc_test_suite and rtc_cc_test " This reverts commit cfe2b7818cf0e8cb26caf765cb77fef751c36a61. Reason for revert: breaks downstream bots Original change's description: > Introduce rtc_test_suite and rtc_cc_test > > rtc_cc_test represents a single test or a small collection of tests. It > generates both an rtc_library to be included in an rtc_test or > rtc_test_suite, as well as a standalone rtc_test to run those few tests. > > rtc_test_suite represents a collection of tests and produces a binary > containing all tests. > > An action is added to confirm that an rtc_cc_test is included in an > rtc_test_suite. If this is not the case, one may not compile the > standalone test binary for the unit test. > > These new templates will replace the monolithic rtc_test/rtc_library > to allow for faster test execution. > > Bug: webrtc:498394143 > Change-Id: Id3fb3108449bd9c73bc0e7f674d7a97f6a6a6964 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/461480 > Reviewed-by: Jeremy Leconte <jleconte@google.com> > Commit-Queue: Evan Shrubsole <eshr@webrtc.org> > Cr-Commit-Position: refs/heads/main@{#47352} Bug: webrtc:498394143 Change-Id: Iac7ddf907e429375b435ec36f6aa3086ce792525 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/462460 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Reviewed-by: Evan Shrubsole <eshr@webrtc.org> Reviewed-by: Jeremy Leconte <jleconte@google.com> Commit-Queue: Philip Eliasson <philipel@webrtc.org> Cr-Commit-Position: refs/heads/main@{#47363}
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.