Moving SwiftShader from component to bundled library

chrome/tools/build/win/FILES.cfg

Index: chrome/tools/build/win/FILES.cfg
diff --git a/chrome/tools/build/win/FILES.cfg b/chrome/tools/build/win/FILES.cfg
index 74ec2abb4c8d40ff8cd4c70f6048fae06a6f214d..7d549db4115078e25bf856d566f5d005c7928724 100644
--- a/chrome/tools/build/win/FILES.cfg
+++ b/chrome/tools/build/win/FILES.cfg
@@ -382,6 +382,17 @@ FILES = [
     'buildtype': ['dev', 'official'],
     'filegroup': ['default', 'symsrc'],
   },
+  # SwiftShader files:
+  {
+    'filename': 'swiftshader/libEGL.dll',

[grt (UTC plus 2), 2017/02/23 15:00:50]

are there pdb files for these as well?

[sugoi, 2017/02/23 15:22:55]

Yes, I think so (I'm not in front of my Windows desktop at the moment, but I
think that there are pdb files generated in the out\Default\swiftshader
directory).

[grt (UTC plus 2), 2017/02/23 15:33:38]

In that case, please add stanzas for the .pdbs as well (see chrome.dll.pdb for
an example).

+    'buildtype': ['dev', 'official'],
+    'filegroup': ['default', 'symsrc'],
+  },
+  {
+    'filename': 'swiftshader/libGLESv2.dll',
+    'buildtype': ['dev', 'official'],
+    'filegroup': ['default', 'symsrc'],
+  },

[Ken Russell (switch to Gerrit), 2017/02/23 01:58:05]

There are conditions like BUILDFLAG(ENABLE_SWIFTSHADER) throughout the code but
I don't see similar conditions in the bundling files. What's the situation here?

[sugoi, 2017/02/23 03:41:31]

Not sure yet, I'm not super knowledgeable about how to configure this file. That
being said, this file is for Windows and ENABLE_SWIFTSHADER is defined as
"is_chrome_branded && is_win", which is what this file is used for, if I
understand correctly.

   # Native Client plugin files:
   {
     'filename': 'nacl_irt_x86_32.nexe',