Add support for references in different paths in apis

build/json_schema_bundle_compile.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.
 
 {
   'variables': {
     # 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:
     #     A Python string substituion pattern used to generate the C++
     #     namespace for each API. Use %(namespace)s to replace with the API
     #     namespace, like "toplevel::%(namespace)s_api".
     #
     # Functions and namespaces can be excluded by setting "nocompile" to true.
     # The default root path of API implementation sources is
     # chrome/browser/extensions/api and can be overridden by setting "impl_dir".
     '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': [
     {
       # GN version: //extensions/generated_extensions_api.gni
       'action_name': 'genapi_bundle',
       'inputs': [
         '<(api_gen_dir)/cc_generator.py',
         '<(api_gen_dir)/code.py',
         '<(api_gen_dir)/compiler.py',
         '<(api_gen_dir)/cpp_bundle_generator.py',
@@ skipping 14 matching lines @@
         '<(SHARED_INTERMEDIATE_DIR)/<(cc_dir)/generated_schemas.cc',
       ],
       'action': [
         'python',
         '<(api_gen)',
         '--root=<(DEPTH)',
         '--destdir=<(SHARED_INTERMEDIATE_DIR)',
         '--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)',
       ],
       'message': 'Generating C++ API bundle code',
       '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,
 }