Remove Android JVM init from pc and SDP tests On Android, the peer connection unit tests and webrtc_sdp_unittest call InitializeAndroidObjects(), which crashes unless a JVM is present. These tests can therefore only run as APKs started by the JNI test launcher. The initialization is not needed: the tests use fake audio devices and fake media engines, SSL is already initialized by the test main, and none of the code they exercise uses webrtc::JVM. Removing the calls, and the android_black_magic target that provided them, allows these tests to run as plain native executables on Android, which are much cheaper to build than APKs. Bug: webrtc:498394143 Change-Id: I5e6b1ce3ad3a03869c8cca93b7ad0dcfe35f45db Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/510780 Reviewed-by: Fredrik Solenberg <solenberg@webrtc.org> Commit-Queue: Fredrik Solenberg <solenberg@webrtc.org> Cr-Commit-Position: refs/heads/main@{#49015}
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.