mirror of
https://github.com/mollyim/webrtc.git
synced 2025-05-15 06:40:43 +01:00
654320666d
Using fully qualified paths to include libyuv headers allows WebRTC to avoid to rely on the //third_party/libyuv:libyuv_config target to set the -I compiler flag. Today some WebRTC targets depend on //third_party/libyuv only to include //third_party/libyuv:libyuv_config but with fully qualified paths this should not be needed anymore. A follow-up CL will remove //third_party/libyuv from some targets that don't need it because they are not including libyuv headers. Bug: webrtc:8605 Change-Id: Icec707ca761aaf2ea8088e7f7a05ddde0de2619a No-Try: True Reviewed-on: https://webrtc-review.googlesource.com/28220 Commit-Queue: Mirko Bonadei <mbonadei@webrtc.org> Reviewed-by: Magnus Flodman <mflodman@webrtc.org> Cr-Commit-Position: refs/heads/master@{#21209} |
||
|---|---|---|
| .. | ||
| api/org/webrtc | ||
| instrumentationtests | ||
| src | ||
| tests/src/org/webrtc | ||
| AndroidManifest.xml | ||
| BUILD.gn | ||
| OWNERS | ||
| PRESUBMIT.py | ||
| 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, 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/.