platform-external-webrtc

Files

magjed b2d1c5026d SurfaceViewRenderer: Add resource name to log outputs and exceptions

Add resource name to log outputs to distinguish local renderer from remote renderer.

This Cl also adds some thread checks and factors out a small helper function makeBlack().

Review URL: https://codereview.webrtc.org/1420203003

Cr-Commit-Position: refs/heads/master@{#10596}

2015-11-11 11:06:49 +00:00

android/org/webrtc

SurfaceViewRenderer: Add resource name to log outputs and exceptions

2015-11-11 11:06:49 +00:00

jni

Support VP9 HW video decoding on Android.

2015-11-10 18:25:59 +00:00

src/org/webrtc

Support VP9 HW video decoding on Android.

2015-11-10 18:25:59 +00:00

testcommon/src/org/webrtc

Java binding for RtpSender/RtpReceiver.

2015-10-06 19:29:32 +00:00

README

Adds trunk/talk folder of revision 359 from libjingles google code to

2013-07-10 00:45:36 +00:00

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, build with 
OS=linux or OS=android and include
build_with_libjingle=1 build_with_chromium=0
in $GYP_DEFINES.

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 jni/.

An example command-line to build & run the unittest:
cd path/to/trunk
GYP_DEFINES="build_with_libjingle=1 build_with_chromium=0 java_home=path/to/JDK" gclient runhooks && \
    ninja -C out/Debug libjingle_peerconnection_java_unittest && \
    ./out/Debug/libjingle_peerconnection_java_unittest
(where path/to/JDK should contain include/jni.h)

During development it can be helpful to run the JVM with the -Xcheck:jni flag.