OLD | NEW |
1 This directory holds a Java implementation of the webrtc::PeerConnection API, as | 1 This directory holds a Java implementation of the webrtc::PeerConnection API, as |
2 well as the JNI glue C++ code that lets the Java implementation reuse the C++ | 2 well as the JNI glue C++ code that lets the Java implementation reuse the C++ |
3 implementation of the same API. | 3 implementation of the same API. |
4 | 4 |
5 To build the Java API and related tests, build with | 5 To build the Java API and related tests, build with OS=android in $GYP_DEFINES. |
6 OS=linux or OS=android and include | |
7 build_with_libjingle=1 build_with_chromium=0 | |
8 in $GYP_DEFINES. | |
9 | 6 |
10 To use the Java API, start by looking at the public interface of | 7 To use the Java API, start by looking at the public interface of |
11 org.webrtc.PeerConnection{,Factory} and the org.webrtc.PeerConnectionTest. | 8 org.webrtc.PeerConnection{,Factory} and the org.webrtc.PeerConnectionTest. |
12 | 9 |
13 To understand the implementation of the API, see the native code in jni/. | 10 To understand the implementation of the API, see the native code in jni/. |
14 | |
15 An example command-line to build & run the unittest: | |
16 cd path/to/trunk | |
17 GYP_DEFINES="build_with_libjingle=1 build_with_chromium=0 java_home=path/to/JDK"
gclient runhooks && \ | |
18 ninja -C out/Debug libjingle_peerconnection_java_unittest && \ | |
19 ./out/Debug/libjingle_peerconnection_java_unittest | |
20 (where path/to/JDK should contain include/jni.h) | |
21 | |
22 During development it can be helpful to run the JVM with the -Xcheck:jni flag. | |
23 | |
OLD | NEW |