IDL build: Split global constructors into core and modules

Source/bindings/core/v8/generated.gyp

Index: Source/bindings/core/v8/generated.gyp
diff --git a/Source/bindings/core/v8/generated.gyp b/Source/bindings/core/v8/generated.gyp
index 52ba2840dcd9ddf66e0255397b05c6d46fe2c05b..44dfd1601b6c65a7cfc9db2b003604bc2052ff6c 100644
--- a/Source/bindings/core/v8/generated.gyp
+++ b/Source/bindings/core/v8/generated.gyp
@@ -9,24 +9,19 @@
 {
   'includes': [
     '../../../core/core.gypi',
+    # FIXME: shouldn't depend on modules  http://crbug.com/358074
+    '../../../modules/modules.gypi',
     '../../bindings.gypi',
-    # FIXME: need list of modules IDL files because some core IDL files depend
-    # on modules IDL files  http://crbug.com/358074
-    '../../modules/idl.gypi',
     # FIXME: need info about modules IDL files because some core IDL files
     # depend on modules IDL files  http://crbug.com/358074
+    '../../modules/idl.gypi',
     '../../modules/modules.gypi',
     '../../scripts/scripts.gypi',
+    '../generated.gypi',
     '../idl.gypi',
     'generated.gypi',
   ],
 
-  # Write lists of main IDL files to a file, so that the command lines don't
-  # exceed OS length limits.
-  'variables': {
-      'core_idl_files_list': '<|(core_idl_files_list.tmp <@(core_idl_files))',
-  },
-
   'targets': [
 ################################################################################
   {
@@ -37,6 +32,10 @@
     'hard_dependency': 1,
     'dependencies': [

[haraken, 2014/06/02 15:45:14]

Just a question about GYP: What is "dependencies"? What's a relationship between
"dependencies" and "includes"?

[Nils Barth (inactive), 2014/06/03 01:47:50]

Short answer:
'dependencies': This lists other targets that this target depends on.
'includes': A list of of other files that will be included in this file.

Dependencies create the edges of the build dependency graph;
includes are just about factoring the .gyp/.gypi files to avoid
duplication.

Long answer (quoting docs):
'dependencies': This lists other targets that this target depends on. The
gyp-generated files will guarantee that the other targets are built before this
target. Any library targets in the dependencies list will be linked with this
target. The various settings (defines, include_dirs, etc.) listed in the
direct_dependent_settings sections of the targets in this list will be applied
to how this target is built and linked. See the more complete discussion of
direct_dependent_settings, below.

'includes': A list of of other files that will be included in this file. By
convention, included files have the suffix .gypi (gyp include).

References:
https://code.google.com/p/gyp/wiki/GypUserDocumentation

       '../../../core/core_generated.gyp:generated_testing_idls',
+      '../generated.gyp:core_global_constructors_idls',
+      # FIXME: should not depend on modules, but partial interface definitions
+      # in modules change bindings for core http://crbug.com/358074
+      '../generated.gyp:modules_global_constructors_idls',
       '<(bindings_scripts_dir)/scripts.gyp:cached_jinja_templates',
       '<(bindings_scripts_dir)/scripts.gyp:cached_lex_yacc_tables',
       # FIXME: should be interfaces_info_core (w/o modules)