Make setup.exe compatible with the component build.

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 2814 matching lines @@
                   },
                 ],
               ],
             },
           ],
           ['component=="static_library"', {
             'defines': [
               '_HAS_EXCEPTIONS=0',
             ],
           }],
+          # To support installing a component build (where the DLLs are not in
+          # same directory as chrome.exe and setup.exe):

[rvargas (doing something else), 2012/05/16 01:09:58]

What does this exactly mean? I don't think this is going to work, does it?

[gab, 2012/05/16 01:15:54]

It will, but not this way. Follow
https://chromiumcodereview.appspot.com/10399041/ if you're intrigued.

+          # create_installer_archive.py writes custom manifests for all the
+          # DLLs. The setting below prevents VS from automatically generating
+          # the usual manifests for those DLLs which would override the custom
+          # external manifests.
+          ['component=="shared_library"', {
+            'target_conditions': [
+              ['_type=="shared_library"', {
+                'msvs_settings': {
+                  'VCLinkerTool': {
+                    'GenerateManifest': 'false',
+                  },
+                },
+              }],
+            ],
+          }],
           ['MSVS_VERSION=="2008"', {
             'defines': [
               '_HAS_TR1=0',
             ],
           }],
           ['secure_atl', {
             'defines': [
               '_SECURE_ATL',
             ],
           }],
@@ skipping 215 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',
   },
 }