platform-external-webrtc

Files

Niels Möller 2b781bf908 Deprecate write-only member CodecInfo::is_hardware_accelerated

This member of the CodecInfo struct was set in several places, but not
used for anything. To aid deletion, this cl defines a default implementation
of VideoEncoderFactory::QueryVideoEncoder.

The next step is to delete almost all downstream implementations of that method,
since the only classes that have to implement it are the few factories that
produce "internal source" encoders, e.g., for Chromium remoting.

Bug: None
Change-Id: I1f0dbf0d302933004ebdc779460cb2cb3a894e02
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/179520
Reviewed-by: Kári Helgason <kthelgason@webrtc.org>
Reviewed-by: Sami Kalliomäki <sakal@webrtc.org>
Reviewed-by: Sebastian Jansson <srte@webrtc.org>
Commit-Queue: Niels Moller <nisse@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#31844}

2020-08-04 07:56:49 +00:00

api/org/webrtc

Use Android Q API to test if MediaCodecInfo is HW Accelerated

2020-07-14 08:57:52 +00:00

instrumentationtests

Roll chromium_revision 4d95e6c77b..71a0e1904e (776481:782339)

2020-06-26 05:33:14 +00:00

native_api

Reland "Pass NetworkMonitorFactory through PeerConnectionFactory."

2020-08-01 00:36:27 +00:00

native_unittests

Reland "Pass NetworkMonitorFactory through PeerConnectionFactory."

2020-08-01 00:36:27 +00:00

src

Deprecate write-only member CodecInfo::is_hardware_accelerated

2020-08-04 07:56:49 +00:00

tests

Roll chromium_revision 4d95e6c77b..71a0e1904e (776481:782339)

2020-06-26 05:33:14 +00:00

AndroidManifest.xml

Roll chromium_revision 4d95e6c77b..71a0e1904e (776481:782339)

2020-06-26 05:33:14 +00:00

BUILD.gn

Remove dependency from audio_jni to built in codecs.

2020-07-28 15:07:14 +00:00

OWNERS

Remove inactive OWNERS.

2020-02-19 13:37:36 +00:00

PRESUBMIT.py

…

README

Updating android/README.

2018-03-01 20:22:48 +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, make sure you have a WebRTC checkout
with Android specific parts. This can be used for linux development as well by
configuring gn appropriately, as it is a superset of the webrtc checkout:
fetch --nohooks webrtc_android
gclient sync

You also must generate GN projects with:
--args='target_os="android" target_cpu="arm"'

More information on getting the code, compiling and running the AppRTCMobile
app can be found at:
https://webrtc.org/native-code/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 src/jni/pc/.