mirror of
https://github.com/mollyim/webrtc.git
synced 2025-05-15 14:50:39 +01:00
![]() Limited range seems to be more used than full range and many Android components already use limited range. This includes FileVideoCapturer, VideoFileRenderer and HW codecs. Bug: webrtc:9638 Change-Id: Iadd9b2f19020c6a25bde5e43a28e26a6230dde42 Reviewed-on: https://webrtc-review.googlesource.com/94543 Commit-Queue: Sami Kalliomäki <sakal@webrtc.org> Reviewed-by: Magnus Jedvert <magjed@webrtc.org> Cr-Commit-Position: refs/heads/master@{#24576} |
||
---|---|---|
.. | ||
api/org/webrtc | ||
instrumentationtests | ||
native_api | ||
native_unittests | ||
src | ||
tests/src/org/webrtc | ||
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/.