IDL build: Split global constructors into core and modules

Source/bindings/core/idl.gypi

Index: Source/bindings/core/idl.gypi
diff --git a/Source/bindings/core/idl.gypi b/Source/bindings/core/idl.gypi
index 6ab9f4ae7d4190bd48c4d0166f8b2a52a843f172..b4d1842b90dc5a680597edf20274ef426f1dc42b 100644
--- a/Source/bindings/core/idl.gypi
+++ b/Source/bindings/core/idl.gypi
@@ -7,7 +7,7 @@
 {
   'includes': [
     '../../core/core.gypi',
-    '../idl.gypi',
+    'generated.gypi',

[haraken, 2014/06/03 15:31:10]

- Why does idl.gypi need to include Source/core/core.gypi and
Source/bindings/core/generated.gypi? I wonder IDL files don't depend on
anything.

- If idl.gypi needs to include Source/core/core.gypi and
Source/bindings/core/generated.gypi, why does idl.gypi not need to include
Source/core/generated.gypi?

[Nils Barth (inactive), 2014/06/04 03:36:31]

Because that's where the IDL files are listed.
(You mean Source/core/*core_*generated.gypi)
Because there are no IDL files defined there:
core does not generate any IDL files.

   ],
 
   'variables': {
@@ -19,6 +19,10 @@
       '<@(generated_webcore_testing_idl_files)',
     ],
 
+    # Write lists of main IDL files to a file, so that the command lines don't
+    # exceed OS length limits.
+    'core_idl_files_list': '<|(core_idl_files_list.tmp <@(core_idl_files))',
+
     # Dependency IDL files: don't generate individual bindings, but do process
     # in IDL dependency computation, and count as build dependencies
     # 'core_dependency_idl_files' is already used in Source/core, so avoid
@@ -61,9 +65,7 @@
     ],
 
     'core_generated_dependency_idl_files': [
-      # FIXME: Generate separate core_global_constructors_idls
-      # http://crbug.com/358074
-      '<@(generated_global_constructors_idl_files)',  # partial interfaces
+      '<@(core_global_constructors_generated_idl_files)',  # partial interfaces
     ],
   },
 }