Initial code generation for features.

build/features_compile.gypi

Index: build/features_compile.gypi
diff --git a/build/features_compile.gypi b/build/features_compile.gypi
new file mode 100644
index 0000000000000000000000000000000000000000..fcdb2b8836d20e8d0d2a5dd2da4c7a97eccbdcc9
--- /dev/null
+++ b/build/features_compile.gypi
@@ -0,0 +1,60 @@
+# Copyright (c) 2013 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.
+
+{
+  'variables': {
+    # When including this gypi, the following variables must be set:
+    #   schema_files: a list of json or IDL files that comprise the features model.
+    #   cc_dir: path to generated files
+    #   root_namespace: the C++ namespace that all generated files go under
+    'feature_gen_dir': '<(DEPTH)/tools/json_schema_compiler',
+    'feature_gen': '<(feature_gen_dir)/features_compiler.py',
+  },
+  'rules': [
+    {
+      'rule_name': 'genfeature',
+      'msvs_external_rule': 1,
+      'extension': 'json',
+      'inputs': [
+        '<(feature_gen_dir)/features_cc_generator.py',
+        '<(feature_gen_dir)/code.py',
+        '<(feature_gen_dir)/features_compiler.py',
+        '<(feature_gen_dir)/cpp_util.py',
+        '<(feature_gen_dir)/features_h_generator.py',
+        '<(feature_gen_dir)/json_schema.py',
+        '<(feature_gen_dir)/model.py',
+        '<(feature_gen_dir)/util.cc',
+        '<(feature_gen_dir)/util.h',
+        '<(feature_gen_dir)/util_cc_helper.py',
+        '<@(schema_files)',
+      ],
+      'outputs': [
+        '<(SHARED_INTERMEDIATE_DIR)/<(cc_dir)/<(RULE_INPUT_ROOT).cc',

[dhnishi (use Chromium), 2013/09/20 16:46:51]

The schema file used right now is the "_permission_features.json". The issue is
that the Python strips the leading underscore, but I can't seem to find a way to
coax GYP into stripping it, so it looks for a corresponding generated
_permission_features.cc/h, doesn't find it, then fails the compile. My build
compile was passing because it still had the "_permission_features" generated
files from previous runs.

I can think of a couple of solutions, but I'm not fond of any of them.

1. Fake the generated file -- if an underscore is stripped, create a dummy file
with the underscore leading the file name in the generated folder.
2. Try to manually add in the outputs and not have it in there using the
RULE_INPUT_*.
3. Do not strip the _ in the generated file.

+        '<(SHARED_INTERMEDIATE_DIR)/<(cc_dir)/<(RULE_INPUT_ROOT).h',
+      ],
+      'action': [
+        'python',
+        '<(feature_gen)',
+        '<(RULE_INPUT_PATH)',
+        '--root=<(DEPTH)',
+        '--destdir=<(SHARED_INTERMEDIATE_DIR)',
+        '--namespace=<(root_namespace)',
+      ],
+      'message': 'Generating C++ feature code from <(RULE_INPUT_PATH) json files',
+      'process_outputs_as_sources': 1,
+    },
+  ],
+  'include_dirs': [
+    '<(SHARED_INTERMEDIATE_DIR)',
+    '<(DEPTH)',
+  ],
+  'direct_dependent_settings': {
+    'include_dirs': [
+      '<(SHARED_INTERMEDIATE_DIR)',
+    ]
+  },
+  # This target exports a hard dependency because it generates header
+  # files.
+  'hard_dependency': 1,
+}