mac: Add the flag "-gline-tables-only" to reduce dSYM size.

build/common.gypi

 # Copyright (c) 2012 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.
 
 # IMPORTANT:
 # Please don't directly include this file if you are building via gyp_chromium,
 # since gyp_chromium is automatically forcing its inclusion.
 {
   # Variables expected to be overriden on the GYP command line (-D) or by
   # ~/.gyp/include.gypi.
@@ skipping 5112 matching lines @@
           'OTHER_CFLAGS': [
             # Someday this can be replaced by an 'GCC_STRICT_ALIASING': 'NO'
             # xcode_setting, but not until all downstream projects' mac bots are
             # using xcode >= 4.6, because that's when the default value of the
             # flag in the compiler switched.  Pre-4.6, the value 'NO' for that
             # setting is a no-op as far as xcode is concerned, but the compiler
             # behaves differently based on whether -fno-strict-aliasing is
             # specified or not.
             '-fno-strict-aliasing',  # See http://crbug.com/32204.
           ],
+          'conditions': [
+            ['branding=="Chrome" and buildtype=="Official"', {
+              'OTHER_CFLAGS': [

[erikchen, 2015/04/23 01:20:36]

I don't understand GYP. I figured that this would override the previous
declaration of OTHER_CFLAGS, but it appears to do the right thing.

[Nico, 2015/04/23 01:26:24]

gyp merges lists by appending them. This is documented at
https://code.google.com/p/gyp/wiki/InputFormatReference#Merge_Basics_(=,_?,_+)

[erikchen, 2015/04/23 01:57:49]

I see. It was unclear to me that lists got merged by default. 

+                # The Google Chrome Framework dSYM generated by dsymutil has grown
+                # larger than 4GB, which dsymutil can't handle. Reduce the amount
+                # of debug symbols.
+                '-gline-tables-only',  # See http://crbug.com/479841
+              ]
+            }],
+          ],
+
         },
         'target_conditions': [
           ['_type=="executable"', {
             'postbuilds': [
               {
                 # Arranges for data (heap) pages to be protected against
                 # code execution when running on Mac OS X 10.7 ("Lion"), and
                 # ensures that the position-independent executable (PIE) bit
                 # is set for ASLR when running on Mac OS X 10.5 ("Leopard").
                 'variables': {
@@ skipping 44 matching lines @@
              _type=="loadable_module") and mac_strip!=0', {
             'target_conditions': [
               ['mac_real_dsym == 1', {
                 # To get a real .dSYM bundle produced by dsymutil, set the
                 # debug information format to dwarf-with-dsym.  Since
                 # strip_from_xcode will not be used, set Xcode to do the
                 # stripping as well.
                 'configurations': {
                   'Release_Base': {
                     'xcode_settings': {
                       'DEBUG_INFORMATION_FORMAT': 'dwarf-with-dsym',

[Nico, 2015/04/23 01:26:24]

Probably best to put this here, next to the dsymutil bits?

[erikchen, 2015/04/23 01:56:05]

This is a good suggestion, not bikeshedding. Thanks! This reduces the number of
instances of "-gline-tables-only" in ninja files from 2k+ to ~150.

                       'DEPLOYMENT_POSTPROCESSING': 'YES',
                       'STRIP_INSTALLED_PRODUCT': 'YES',
                       'conditions': [
                         # Only strip non-ASan builds.
                         ['asan==0', {
                           'target_conditions': [
                             ['_type=="shared_library" or _type=="loadable_module"', {
                               # The Xcode default is to strip debugging symbols
                               # only (-S).  Local symbols should be stripped as
                               # well, which will be handled by -x.  Xcode will
@@ skipping 919 matching lines @@
     # settings in target dicts.  SYMROOT is a special case, because many other
     # Xcode variables depend on it, including variables such as
     # PROJECT_DERIVED_FILE_DIR.  When a source group corresponding to something
     # like PROJECT_DERIVED_FILE_DIR is added to a project, in order for the
     # files to appear (when present) in the UI as actual files and not red
     # red "missing file" proxies, the correct path to PROJECT_DERIVED_FILE_DIR,
     # and therefore SYMROOT, needs to be set at the project level.
     'SYMROOT': '<(DEPTH)/xcodebuild',
   },
 }