aboutsummaryrefslogtreecommitdiffhomepage
path: root/BUILD.gn
diff options
context:
space:
mode:
authorGravatar Leon Scroggins III <scroggo@google.com>2017-07-11 15:53:41 -0400
committerGravatar Leon Scroggins <scroggo@google.com>2017-07-11 20:43:35 +0000
commit51b2f1b64c4d250e15b33ea390b4a95c50afc5dd (patch)
tree47aba850516f0696761602d24c7435674d36be0e /BUILD.gn
parent7e49d534d71d3e7b053fe6f23dfe018ddbceb45b (diff)
Stop adding Android-specific defines to SkUserConfig
Remove #defines that lived in gn_to_bp.py and android_framework_defines.gni. These have been moved into a new file in Android, SkUserConfigManual.h, in https://googleplex-android-review.git.corp.google.com/#/c/2519600/ Update gn_to_bp.py to include SkUserConfigManual.h, so it will still result in using the same #defines. Lately, we've found it difficult to guard changes behind a flag. e.g. a change to drawing causes a CTS failure in Android, so we have to do the following: - put the change behind a flag, and add it to gn_to_bp.py or android_framework_defines.gni - generate new images on Android (by running CTS with external/skia modified to not define the flag) - create a CL in CTS that uses the new images - land a CL in Skia that stops defining the flag - when the Skia change lands, wait for the auto-roller to create a CL that includes the change, stop the auto-roller, add the topic to the CTS CL so the two can land at the same time - land both Android changes (with TreeHugger) - restart the Android auto-roller With SkUserConfigManual.h (which lives in Android), the process will be similar to Chromium: - land a CL in Android's external/skia that defines a flag e.g. SK_SUPPORT_LEGACY_FEATURE. Land without TreeHugger because it isn't used in Skia and does not do anything - land a change in Skia that changes behavior unless SK_SUPPORT_LEGACY_FEATURE is defined. This will safely go through the Android roll and not change any behavior for Android - create two Android CLs - one in CTS to use the new images, and one in external/skia to delete SK_SUPPORT_LEGACY_FEATURE. Set them to the same topic and land them with TreeHugger In the new process, there is no need to mess with the Android roll. A downside to the new process is that we cannot test the android framework defines without checking in to Android. But given how much we've progressed in automating Android testing, this is fine. Bug: b/63429612 Change-Id: Idfbaef2f4cae641a75fb6e7bf70428733a441336 Reviewed-on: https://skia-review.googlesource.com/22072 Commit-Queue: Leon Scroggins <scroggo@google.com> Reviewed-by: Eric Boren <borenet@google.com>
Diffstat (limited to 'BUILD.gn')
-rw-r--r--BUILD.gn5
1 files changed, 0 insertions, 5 deletions
diff --git a/BUILD.gn b/BUILD.gn
index dc8cca03c1..7be16ef514 100644
--- a/BUILD.gn
+++ b/BUILD.gn
@@ -3,7 +3,6 @@
# Use of this source code is governed by a BSD-style license that can be
# found in the LICENSE file.
-import("gn/android_framework_defines.gni")
import("gn/shared_sources.gni")
if (is_fuchsia) {
@@ -33,7 +32,6 @@ declare_args() {
skia_use_metal = false
skia_android_serial = ""
- skia_enable_android_framework_defines = false
skia_enable_discrete_gpu = true
skia_enable_effects = true
skia_enable_gpu = true
@@ -114,9 +112,6 @@ config("skia_public") {
if (is_fuchsia || is_linux) {
defines += [ "SK_SAMPLES_FOR_X" ]
}
- if (skia_enable_android_framework_defines) {
- defines += android_framework_defines
- }
if (!skia_enable_gpu) {
defines += [ "SK_SUPPORT_GPU=0" ]
}