build/java_cpp_template.gypi: new build rules.

build/android/java_cpp_template.gypi

+# Copyright (c) 2012 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.
+
+# This file is meant to be included into a target to provide a rule
+# to generate Java source files from templates that are processed
+# through the host C pre-processor.
+#
+# This assumes a GNU-compatible pre-processor installed as 'cpp'.
+# Only tested on Linux.
+#
+# To use this, create a gyp target with the following form:
+#  {
+#    'target_name': 'android_net_java_constants',
+#    'type': 'none',
+#    'sources': [
+#      'net/base/certificate_mime_type_list.h',
+#      'net/android/NetError.template',
+#    ],
+#    'variables': {
+#      'package_name': 'org.chromium.net',
+#    },
+#    'includes': [ '../build/android/java_constants.gypi' ],
+#  },
+#
+# The 'sources' entry should list all input files. The template file
+# itself should use the 'ClassName.template' format, and will generate
+# 'gen/templates/<package-name>/ClassName.java. Other source files
+# are those typically included by the template. Any change to them
+# will force a rebuild of the template, and hence of any source that
+# depends on it.
+#
+
+{
+  # Location where all generated Java sources will be placed.
+  'variables': {
+    'output_dir': '<(SHARED_INTERMEDIATE_DIR)/templates/<(package_name)'
+  },
+  # Ensure that the output directory is used in the class path
+  # when building targets that depend on this one.
+  'direct_dependent_settings': {
+    'variables': {
+      'generated_src_dirs': [
+        '<(output_dir)/',
+      ],
+    },
+  },
+  # Define a single rule that will be apply to each .template file
+  # listed in 'sources'.
+  'rules': [
+    {
+      'rule_name': 'generate_java_constants',
+      'extension': 'template',
+      # Ensure the generated Java file is treated as input to the targets
+      # that depend on it.
+      'direct_dependent_settings': {
+        'variables': {
+          'additional_input_paths': [
+            '<(output_dir)/<(RULE_INPUT_ROOT).java'
+          ],
+        },
+      },

[Ryan Sleevi, 2012/12/05 17:44:52]

This doesn't work - and if it does, it's a GYP bug, and you shouldn't depend on
it.

'rules' don't have 'dependencies', so you cannot do this.

[digit1, 2012/12/06 14:16:29]

I see. I've scanned all gyp files in the project and indeed this seems to be
true.

The 'additional_input_paths' was part of the original un-rules-using gyp
fragment, but I've checked that it can be safely removed here (i.e. this doesn't
affect clean or incremental builds). Fixed in the last patch.

Thanks

+      'outputs': [
+        '<(output_dir)/<(RULE_INPUT_ROOT).java'
+      ],
+      'action': [
+        'cpp',                 # invoke host pre-processor.
+        '-x', 'c-header',      # treat sources as C header files
+        '-P',                  # disable line markers, i.e. '#line 309'
+        '-I', '<(DEPTH)',      # Add project top-level to include path
+        '-o', '<@(_outputs)',  # Specify output file
+        '<(RULE_INPUT_PATH)',  # Specify input file
+      ],
+      'message': 'Generating Java from cpp template <(RULE_INPUT_PATH)',
+    }
+  ],
+}