mirror of
https://github.com/mollyim/webrtc.git
synced 2025-05-19 00:27:51 +01:00
![]() This allows forcing a minimum frame rate if the producer doesn’t update the SurfaceTexture often. This needs to be done in SurfaceTextureHelper to keep the synchronization of the texture access consistent. Bug: b/149383039 Change-Id: I0e3c82dd51d486b931bd8dda0fd9d5cdb1a90901 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/177001 Reviewed-by: Sami Kalliomäki <sakal@webrtc.org> Commit-Queue: Xavier Lepaul <xalep@google.com> Cr-Commit-Position: refs/heads/master@{#31504} |
||
---|---|---|
.. | ||
api/org/webrtc | ||
instrumentationtests | ||
native_api | ||
native_unittests | ||
src | ||
tests | ||
AndroidManifest.xml | ||
BUILD.gn | ||
OWNERS | ||
PRESUBMIT.py | ||
README |
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/.