From 7e2c89ce97570408fd624a4e1474cfa1ff3705ae Mon Sep 17 00:00:00 2001 From: Mirko Bonadei Date: Mon, 13 Mar 2023 11:17:28 +0100 Subject: [PATCH] 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 Commit-Queue: Mirko Bonadei Reviewed-by: Mirko Bonadei Cr-Commit-Position: refs/heads/main@{#39543} --- .gn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.gn b/.gn index c9824916ad..445772fada 100644 --- a/.gn +++ b/.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