mirror of
https://github.com/DrKLO/Telegram.git
synced 2025-01-09 03:43:36 +01:00
.. | ||
generated_audio_device_module_base_jni | ||
generated_base_jni | ||
generated_builtin_audio_codecs_jni | ||
generated_external_classes_jni | ||
generated_java_audio_device_module_native_jni | ||
generated_java_audio_jni | ||
generated_libaom_av1_jni | ||
generated_libvpx_vp8_jni | ||
generated_libvpx_vp9_jni | ||
generated_logging_jni | ||
generated_metrics_jni | ||
generated_native_api_jni | ||
generated_openh264_jni | ||
generated_peerconnection_jni | ||
generated_video_egl_jni | ||
generated_video_jni | ||
native_api | ||
src/jni | ||
OWNERS | ||
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/.