Integrate syzygy (optionally) into the chrome build process.

chrome/chrome_dll.gypi

 # Copyright (c) 2011 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.
 {
   'target_defaults': {
     'variables': {
       'chrome_dll_target': 0,
     },
     'target_conditions': [
       ['chrome_dll_target==1', {
@@ skipping 116 matching lines @@
 
                 # TODO(sgk):  left-over from pre-gyp build, figure out
                 # if we still need them and/or how to update to gyp.
                 #'app/check_dependents.bat',
                 #'app/chrome.dll.deps',
               ],
               'msvs_settings': {
                 'VCLinkerTool': {
                   'ImportLibrary': '$(OutDir)\\lib\\chrome_dll.lib',
                   'ProgramDatabaseFile': '$(OutDir)\\chrome_dll.pdb',
+                  # This corresponse to the /PROFILE flag which ensures

[Sigurður Ásgeirsson, 2011/07/27 11:21:56]

corresponse -> corresponds?

+                  # the PDB file contains FIXUP information.
+                  'Profile': 'true',

[chrisha, 2011/07/26 23:47:24]

Wasn't this already addressed somewhere else? ie: in base.gyp, or common.gypi?

                 },
               },
             }],  # OS=="win"
             ['OS=="mac"', {
               # The main browser executable's name is <(mac_product_name).
               # Certain things will get confused if two modules in the
               # executable share the same name, so append " Framework" to the
               # product_name used for the framework.  This will result in
               # a name like "Chromium Framework.framework".
               'product_name': '<(mac_product_name) Framework',
@@ skipping 518 matching lines @@
                   'LinkIncremental': '<(msvs_debug_link_nonincremental)',
                 },
               },
             },
           },
         },  # target chrome_dll
       ],
     }],
   ],
 }