277a3b4f85
The default value of sdpSemantics is about to change from PLAN_B to UNIFIED_PLAN. In order not to cause subtle bugs by applications that depend on the default value being PLAN_B, we are temporarily making the default NOT_SPECIFIED. Constructing with NOT_SPECIFIED causes the C++ layer to crash (https://webrtc-review.googlesource.com/c/src/+/242968). This is in accordance to the publically announced plans: https://groups.google.com/u/1/g/discuss-webrtc/c/SdoVP02eUIk While we're at it, we're upgrading almost all unit tests to use Unified Plan. However there are still two tests using Plan B for which I added TODO comments to be dealt with later; not having an Android setup makes it impossible to debug these efficiently. Bug: webrtc:11121 Change-Id: Ib086186bee947d18d31b413e3aeba0cb247b377d Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/246000 Reviewed-by: Harald Alvestrand <hta@webrtc.org> Reviewed-by: Xavier Lepaul <xalep@webrtc.org> Commit-Queue: Henrik Boström <hbos@webrtc.org> Cr-Commit-Position: refs/heads/main@{#35700}
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/.