Reason for revert: webrtc_perf_tests fails on all Android Release testers: http://build.chromium.org/p/client.webrtc/builders/Android64%20Tests%20%28L%20Nexus9%29/builds/3673 Original issue's description: > Roll chromium_revision 7fa6701bc5..1a73d11e65 (398458:399420) > > A fix was needed to make Android tests pass after > https://codereview.chromium.org/2043803003 > > Change log:7fa6701bc5..1a73d11e65> Full diff:7fa6701bc5..1a73d11e65> > Changed dependencies: > * src/buildtools:8dd3c8e39a..099f1da55b> * src/third_party/boringssl/src: https://boringssl.googlesource.com/boringssl.git/+log/0fc7df55c0..171b5403ee > * src/third_party/ffmpeg:7f03319b9d..bcb8b67b8b> DEPS diff:7fa6701bc5..1a73d11e65/DEPS > > No update to Clang. > > TBR= > BUG=webrtc:5990 > NOTRY=True > > Committed: https://crrev.com/c49cf1308f879ce029f5f0e804b4eef3b08b67c5 > Cr-Commit-Position: refs/heads/master@{#13117} TBR= # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=webrtc:5990 Review-Url: https://codereview.webrtc.org/2059423002 Cr-Commit-Position: refs/heads/master@{#13118}
19 lines
939 B
Plaintext
19 lines
939 B
Plaintext
# Copyright (c) 2016 The WebRTC project authors. All Rights Reserved.
|
|
#
|
|
# Use of this source code is governed by a BSD-style license
|
|
# that can be found in the LICENSE file in the root of the source
|
|
# tree. An additional intellectual property rights grant can be found
|
|
# in the file PATENTS. All contributing project authors may
|
|
# be found in the AUTHORS file in the root of the source tree.
|
|
|
|
# See https://bugs.chromium.org/p/webrtc/issues/detail?id=5453.
|
|
# Some WebRTC targets require the 10.7 deployment version of the Mac SDK and a
|
|
# 10.11 min SDK but those targets are only used in non-Chromium builds. We can
|
|
# remove this when Chromium drops 10.6 support and also requires 10.7.
|
|
mac_sdk_min_build_override = "10.11"
|
|
mac_deployment_target_build_override = "10.7"
|
|
|
|
# Variable that can be used to support multiple build scenarios, like having
|
|
# Chromium specific targets in a client project's GN file etc.
|
|
build_with_chromium = false
|