Add support for building the new analyzer using gyp.

editor/analyzer.gyp

Index: editor/analyzer.gyp
===================================================================
--- editor/analyzer.gyp	(revision 0)
+++ editor/analyzer.gyp	(revision 0)
@@ -0,0 +1,112 @@
+# Copyright (c) 2013, the Dart project authors.  Please see the AUTHORS file
+# for details. All rights reserved. Use of this source code is governed by a
+# BSD-style license that can be found in the LICENSE file.
+
+{
+  'targets': [
+    {
+      'target_name': 'analyzer',
+      'type': 'none',
+      'variables': {
+        'analyzer_name': 'new_analyzer',
+        'java_source_files': [
+          '<!@(["python", "../tools/list_files.py", "\\.java$", "tools/plugins/com.google.dart.command.analyze"])',
+          '<!@(["python", "../tools/list_files.py", "\\.java$", "tools/plugins/com.google.dart.engine"])',
+        ],
+        # When changing the jar files that we depend on please change the list
+        # below.
+        'dependent_jar_files': [
+          '../third_party/commons-lang/3.1/commons-lang3-3.1.jar',
+          '../third_party/json/r2_20080312/json.jar',
+          '../third_party/guava/r13/guava-13.0.1.jar',
+          '../third_party/args4j/2.0.12/args4j-2.0.12.jar'
+        ],
+        # We simply rely on all the jar files being copied to the output dir.
+        'compilation_classpath': '<(PRODUCT_DIR)/<(analyzer_name)/*',
+        # The file where we write the class path to be used in the manifest.
+        'class_path_file': '<(PRODUCT_DIR)/<(analyzer_name)/classpath_file',
+        'compilation_command': [

[ahe, 2013/02/14 16:34:10]

Unused.

[ricow1, 2013/02/15 12:01:36]

Done.

+            'javac',
+            '-sourcepath', 'foobar',
+            '-source', '6',
+            '-target', '6',
+            '-implicit:none',
+            '-d', '<(PRODUCT_DIR)/<(analyzer_name)/',
+            '-cp',
+            '<@(compilation_classpath)',
+            '<@(java_source_files)',
+          ],
+      },
+      # Copy all the jar files we depend on to the output directory.
+      'copies': [
+        {
+          'destination': '<(PRODUCT_DIR)/<(analyzer_name)',
+          'files': [
+             '<@(dependent_jar_files)',
+          ],
+        }
+      ],
+      'actions': [
+        {
+          'action_name': 'create_classpath_file',
+          'inputs': [
+            '<@(java_source_files)',
+            '<@(dependent_jar_files)',
+            'tools/write_class_path_file.py'
+          ],
+          'outputs': [
+            '<(PRODUCT_DIR)/<(analyzer_name)/classpath_file',
+          ],
+          'action': [
+            'python', 'tools/write_class_path_file.py',
+            '<(class_path_file)',
+            '<(PRODUCT_DIR)/<(analyzer_name)',
+            '<(analyzer_name)',
+          ],
+          'message': 'Creating  <(_outputs).',
+        },
+        {
+          'action_name': 'create_analyzer',
+          'inputs': [
+            '<@(java_source_files)',
+            '<@(dependent_jar_files)',
+            'tools/compile_analyzer.py',
+          ],
+          'outputs': [
+            '<(PRODUCT_DIR)/<(analyzer_name)/com',

[ahe, 2013/02/14 16:34:10]

This is a directory dependency. I'm not convinced they work. See my comments
below.

[ricow1, 2013/02/15 12:01:36]

I changed this and below to rely on the main file

+          ],
+          'action': [
+            'python',
+            'tools/compile_analyzer.py',
+            '<(PRODUCT_DIR)/<(analyzer_name)/',
+            '<@(compilation_classpath)',
+            '<@(java_source_files)',
+          ],
+          'message': 'Creating <(_outputs).',
+        },
+        {
+          'action_name': 'pack_analyzer',
+          'inputs': [
+            '<@(java_source_files)',
+            '<@(dependent_jar_files)',
+            '<(class_path_file)',
+            '<(PRODUCT_DIR)/<(analyzer_name)/com',
+          ],
+          'outputs': [
+            '<(PRODUCT_DIR)/<(analyzer_name).jar',
+          ],
+          'action': [
+            'jar',

[ahe, 2013/02/14 16:34:10]

Probably needs to be wrapped in a python program. I think I can find a python
program that compiles and creates JAR files in one go.

[ricow1, 2013/02/15 12:01:36]

Done.

+            'cfem', '<(PRODUCT_DIR)/<(analyzer_name).jar',
+            'com.google.dart.command.analyze.AnalyzerMain',
+            '<(class_path_file)',
+            '-C', '<(PRODUCT_DIR)/<(analyzer_name)/', 'com',
+          ],
+          'message': 'Pack analyzer.',
+        },
+      ],
+    }
+  ]
+}
+
+