Migrate standalone tools and loopback tests to LoggingConfig Update standalone command-line tools, loopback test runners, and fuzzer defaults to initialize logging via webrtc::InitializeLogging instead of legacy LogMessage::LogToDebug and SetLogToStderr: - video_loopback - sv_loopback - screenshare_loopback - rtc_event_log_visualizer - rtc_event_log_to_text - video_encoder - data_channel_benchmark - audio_processing_simulator - rnn_vad_tool - webrtc_fuzzer_main Bug: webrtc:42234107 Change-Id: I52a531176a5d2ba09c460a9afecb55c05085b4ee Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/500741 Reviewed-by: Tomas Gunnarsson <tommi@webrtc.org> Commit-Queue: Fredrik Solenberg <solenberg@webrtc.org> Cr-Commit-Position: refs/heads/main@{#48526}
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.