webrtc_m130

History

Magnus Jedvert 1d640e53bd JavaVideoRendererWrapper: Use jlongFromPointer() to convert frame pointer to jlong

The purpose of this CL is to use jlongFromPointer() for converting frame pointers to jlong instead of implicit casts which is not safe.

In order to respect constness, I had to make a small helper function for this.

BUG=webrtc:4993
R=perkj@webrtc.org

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

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

2015-09-29 14:33:27 +00:00

android/org/webrtc

Revert of Android VideoCapturer: Send ByteBuffer instead of byte[] (patchset #1 id:1 of https://codereview.webrtc.org/1372813002/ )

2015-09-29 08:13:47 +00:00

jni

JavaVideoRendererWrapper: Use jlongFromPointer() to convert frame pointer to jlong

2015-09-29 14:33:27 +00:00

src/org/webrtc

Passing the new policy from PeerConnection RTCConfiguration to

2015-09-28 14:57:39 +00:00

testcommon/src/org/webrtc

Adding 20-second timeout to Java and Objective-C tests.

2015-09-28 21:09:00 +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.