Mirko Bonadei 9ea1ef649f Switch from junit_binary to robolectric_binary.
This was done in:
https://chromium-review.googlesource.com/c/chromium/src/+/3709093
https://chromium-review.googlesource.com/c/chromium/src/+/3732850

Bug: chromium:1336818, b/237612564
Change-Id: Ie1394ffa16a7c3322aa774e94aee93e6b1ac6ed6
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/267167
Reviewed-by: Andrey Logvin <landrey@webrtc.org>
Commit-Queue: Mirko Bonadei <mbonadei@webrtc.org>
Auto-Submit: Mirko Bonadei <mbonadei@webrtc.org>
Commit-Queue: Andrey Logvin <landrey@webrtc.org>
Cr-Commit-Position: refs/heads/main@{#37376}
2022-06-30 08:02:18 +00:00
..
2022-06-16 15:55:09 +00:00
2022-03-31 10:48:31 +00:00

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/.