Add support for references in different paths in apis

build/json_schema_bundle_compile.gypi

Index: build/json_schema_bundle_compile.gypi
diff --git a/build/json_schema_bundle_compile.gypi b/build/json_schema_bundle_compile.gypi
index 7e712d7df49e45931305256e7342f98b02d3780e..b46a2bfdc4a78609a70c75641a96e515918dd75b 100644
--- a/build/json_schema_bundle_compile.gypi
+++ b/build/json_schema_bundle_compile.gypi
@@ -7,6 +7,8 @@
     # When including this gypi, the following variables must be set:
     #   schema_files:
     #     An array of json or idl files that comprise the api model.
+    #   schema_includes (optional):
+    #     An array of paths to include when searching for referenced objects.
     #   cc_dir:
     #     The directory to put the generated code in.
     #   root_namespace:
@@ -20,6 +22,7 @@
     'api_gen_dir': '<(DEPTH)/tools/json_schema_compiler',
     'api_gen': '<(api_gen_dir)/compiler.py',
     'impl_dir%': 'chrome/browser/extensions/api',
+    'schema_includes' : [],

[not at google - send to devlin, 2014/08/25 22:22:46]

No space before the :

[lfg, 2014/08/26 16:15:21]

Done.

   },
   'actions': [
     {
@@ -54,6 +57,7 @@
         '--namespace=<(root_namespace)',
         '--generator=cpp-bundle',
         '--impl-dir=<(impl_dir)',
+        '--include=<(schema_includes)',

[not at google - send to devlin, 2014/08/25 22:22:46]

For every time this parameter is passed around, or some form of it:

Can we standardise on a single terminology, whether that be "include" or
"schema-include" or, whatever? I think "include" by itself is too vague,
"include-dir" more accurate but doesn't capture the way that these aren't
actually directories, they're rules which include the namespace with which to
include.

I wish there was a way for gyp to do all of this for us, but, ah well.

So how about "include-rules"?

[lfg, 2014/08/26 16:15:21]

include-rules sounds good, I went with it.

         '<@(schema_files)',
         '<@(non_compiled_schema_files)',
       ],