[Mac/GN] Implement dSYM generation and stripping.

build/config/mac/symbols.gni

Index: build/config/mac/symbols.gni
diff --git a/build/config/mac/symbols.gni b/build/config/mac/symbols.gni
new file mode 100644
index 0000000000000000000000000000000000000000..4e717e8304eb55799d313543e7b6936e762ef199
--- /dev/null
+++ b/build/config/mac/symbols.gni
@@ -0,0 +1,24 @@
+# Copyright 2016 The Chromium Authors. All rights reserved.
+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+
+import("//build/config/chrome_build.gni")
+
+# This file declares arguments and configs that control whether dSYM debug
+# info is produced and whether build products are stripped.
+
+declare_args() {
+  # Produce dSYM files for targets that are configured to do so. By default,
+  # symbol information is retained in the object files because dsymutil is
+  # very slow. Targets interested in having a dSYM file produced can use the
+  # //build/config/mac:dsym config.
+  enable_dsyms = is_official_build
+
+  # Strip symbols from targets that are configured to do so. This should be
+  # used in conjuction with enable_dsyms to ensure that debug information
+  # remains available. The linker driver will produce any dSYMs before
+  # invoking strip. Targets that do not want to keep symbols can use the
+  # //build/config/mac:strip_all config. If targets wish to use a saves file,
+  # they should add the ldflags themselves, conditional on this argument.
+  enable_stripping = is_official_build

[Mark Mentovai, 2016/05/20 15:42:41]

The big problem I see here now is that ordinary “Release” builds won’t give
people the verify_order failures. Do any try/cq-bots run the “official”
configuration? If not, those bad changes will land and then have to be backed
out.

[Robert Sesek, 2016/05/20 19:09:55]

verify_order runs independent of this flag. It's running now, on the bots.

https://code.google.com/p/chromium/codesearch#chromium/src/chrome/BUILD.gn&q=...

+}