357f596558
This will allow clients to include only the software codecs they need rather than being forced to bundle them all. - libjingle_peerconnection_jni keeps its allow_poison for now, until dependent targets bundle their own codecs explicitly. - native_api_codecs and native_api_video lose their allow_poison because dependent targets are already bundling codecs explicitly. - libjingle_peerconnection_metrics_default_jni and native_api_peerconnection lose their allow_poison because they were not actually poisoned. legacy_hwcodecs_jni and default_video_codec_factory_jni exist for clients that want to continue bundling the same codecs they get by default today. Bug: webrtc:7925 Change-Id: Idf853a6bc77f43decd35ad2a0f467937fec8f8b5 Reviewed-on: https://webrtc-review.googlesource.com/c/108221 Reviewed-by: Sami Kalliomäki <sakal@webrtc.org> Commit-Queue: Jonathan Yu <yujo@chromium.org> Cr-Commit-Position: refs/heads/master@{#25564}
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/.