Add option to export tracing events to ETW.

chrome/chrome_dll.gypi

Index: chrome/chrome_dll.gypi
diff --git a/chrome/chrome_dll.gypi b/chrome/chrome_dll.gypi
index db16fa0dfd08c658d450f8a010d86e5dc3e1b0a0..8852a6a62569be7da65a360f8ea7adc793b4c25e 100644
--- a/chrome/chrome_dll.gypi
+++ b/chrome/chrome_dll.gypi
@@ -124,6 +124,7 @@
                 # On Windows, link the dependencies (libraries) that make
                 # up actual Chromium functionality into this .dll.
                 'chrome_version_resources',
+                '../base/trace_event/etw_manifest/etw_manifest.gyp:etw_manifest',
                 '../chrome/chrome_resources.gyp:chrome_unscaled_resources',
                 '../content/app/resources/content_resources.gyp:content_resources',
                 '../crypto/crypto.gyp:crypto',
@@ -133,6 +134,9 @@
               'sources': [
                 'app/chrome_dll.rc',
 
+                # ETW Manifest.
+                '<(SHARED_INTERMEDIATE_DIR)/base/trace_event/etw_manifest/chrome_events_win.rc',

[Lei Zhang, 2015/04/15 08:10:36]

Based on your content/ changes, it looks like the new code is being used in the
renderer process... so do you need to add this to chrome_child.dll as well?

[Georges Khalil, 2015/04/15 15:10:32]

Yes, the code is also being used by renderers. However, this is only needed in
one
dll/exe, as it's used by the external tools to decode the messages. We chose to
put it in Chrome.dll. Having it in an other executable would be redundant.

+
                 '<(SHARED_INTERMEDIATE_DIR)/chrome_version/chrome_dll_version.rc',
 
                 # Cursors.