Mirko Bonadei 4ab100d4a6 Address UnnecessaryParentheses errorprone warnings
These prevent the roll of Chromium, see [1]. This CL is a follow-up of
https://webrtc-review.googlesource.com/c/src/+/363944 which didn't fix
all of the issues.

[1] - https://ci.chromium.org/ui/p/webrtc/builders/try/android_arm64_rel/78025/overview

Bug: None
Change-Id: I68c5ea605ed621dae2494378e74313ba0652c6a2
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/363945
Auto-Submit: Mirko Bonadei <mbonadei@webrtc.org>
Reviewed-by: Harald Alvestrand <hta@webrtc.org>
Commit-Queue: Harald Alvestrand <hta@webrtc.org>
Cr-Commit-Position: refs/heads/main@{#43101}
2024-09-29 06:23:41 +00:00
..
2023-11-07 09:58:37 +00:00
2022-03-31 10:48:31 +00:00

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/.