de5afcfcbf
The generated JNI files are actually implementation files that can only be included from one place. For generating JNI code for PeerConnection.java, this means we need to collect all JNI PeerConnection code into one place. This CL moves peerconnectionobserver_jni.h to peerconnection.h, and merges peerconnectionobserver_jni.cc and peerconnection_jni.cc. It also moves converter functions JavaToNativeIceServers and JavaToNativeRTCConfiguration to peerconnection.h since they are also related to PeerConnection.java. This CL does not contain anything else than a pure code move. TBR=sakal@webrtc.org Bug: webrtc:8278 Change-Id: I31c696c1aab495e09f95e5ba5d79f95df7c34a0e Reviewed-on: https://webrtc-review.googlesource.com/31483 Reviewed-by: Magnus Jedvert <magjed@webrtc.org> Commit-Queue: Magnus Jedvert <magjed@webrtc.org> Cr-Commit-Position: refs/heads/master@{#21200}
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, generate GN projects with:
--args='target_os="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 jni/.