mirror of
https://github.com/mollyim/webrtc.git
synced 2025-05-13 05:40:42 +01:00
c8e0a21126
The regression obseverved on Samung devices the last time was caused by the not detaching the context/surface prior to releasing an EGLSurface or EGLContext. This was fine on most devices but obviously not all. Bug: b/225229697 Change-Id: I1849c772f3ed3e8819c748d997e5261289c4b2bc Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/321842 Commit-Queue: Linus Nilsson <lnilsson@webrtc.org> Reviewed-by: Zoé Lepaul <xalep@webrtc.org> Cr-Commit-Position: refs/heads/main@{#40844} |
||
|---|---|---|
| .. | ||
| api/org/webrtc | ||
| instrumentationtests | ||
| native_api | ||
| native_unittests | ||
| src | ||
| tests | ||
| AndroidManifest.xml | ||
| BUILD.gn | ||
| 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/.