ff616269f8
This commit addresses an issue resulting from a change [1] in the jni_zero project, where the format of classpath entries changed (from using slashes 'org/webrtc/PeerConnectionFactory' to dots 'org.webrtc.PeerConnectionFactory'). These changes led to failures in the Chromium rolls in WebRTC, as the Class loader in JNI was not designed to handle class names with dots. This CL fixes this issue by changing webrtc::GetClass to convert class paths to what JNI expects. [1] https://chromium-review.googlesource.com/c/chromium/src/+/5234469 Bug: chromium:1377351 Change-Id: I2f243bb4ed04136f86510fcd5472e9bfc2d4ba85 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/337900 Reviewed-by: Jeremy Leconte <jleconte@google.com> Reviewed-by: Harald Alvestrand <hta@webrtc.org> Commit-Queue: Jeremy Leconte <jleconte@google.com> Cr-Commit-Position: refs/heads/main@{#41666}
This directory holds a Java implementation of the webrtc::PeerConnection API, as
well as the JNI glue C++ code that lets the Java implementation reuse the C++
implementation of the same API.
To build the Java API and related tests, make sure you have a WebRTC checkout
with Android specific parts. This can be used for linux development as well by
configuring gn appropriately, as it is a superset of the webrtc checkout:
fetch --nohooks webrtc_android
gclient sync
You also must generate GN projects with:
--args='target_os="android" target_cpu="arm"'
More information on getting the code, compiling and running the AppRTCMobile
app can be found at:
https://webrtc.org/native-code/android/
To use the Java API, start by looking at the public interface of
org.webrtc.PeerConnection{,Factory} and the org.webrtc.PeerConnectionTest.
To understand the implementation of the API, see the native code in src/jni/pc/.