mirror of
https://github.com/mollyim/webrtc.git
synced 2025-05-12 21:30:45 +01:00
Increase android32_ndk_api_level to 21.
Chromium has done this in 2021 (https://crrev.com/c/2405530). This will allow the new BoringSSL to roll into WebRTC (since now BoringSSL requires the NDK level to be >= 18). NO_TRY=True Bug: None Change-Id: I4b722aef56cb1e189f4df6de64a87ab1e5b620a1 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/297362 Reviewed-by: Christoffer Jansson <jansson@webrtc.org> Commit-Queue: Mirko Bonadei <mbonadei@webrtc.org> Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> Cr-Commit-Position: refs/heads/main@{#39543}
This commit is contained in:
parent
210b8b2325
commit
7e2c89ce97
1 changed files with 1 additions and 1 deletions
2
.gn
2
.gn
|
@ -52,7 +52,7 @@ default_args = {
|
|||
ios_deployment_target = "12.0"
|
||||
|
||||
# The SDK API level, in contrast, is set by build/android/AndroidManifest.xml.
|
||||
android32_ndk_api_level = 16
|
||||
android32_ndk_api_level = 21
|
||||
android64_ndk_api_level = 21
|
||||
|
||||
# WebRTC does not provide the gflags dependency. Because libyuv uses it only
|
||||
|
|
Loading…
Reference in a new issue