Migrate Declarative API bindings to new JSON objects generated by JSON compiler

chrome/chrome_tests.gypi

Index: chrome/chrome_tests.gypi
diff --git a/chrome/chrome_tests.gypi b/chrome/chrome_tests.gypi
index a116a710d1881ee068987e7b0dbe72e350cdf606..3e50fcdd116dffd31d6a2cd217ca9d1b715e2a98 100644
--- a/chrome/chrome_tests.gypi
+++ b/chrome/chrome_tests.gypi
@@ -2467,6 +2467,7 @@
         'chrome',
         'chrome_resources.gyp:chrome_resources',
         'chrome_resources.gyp:chrome_strings',
+        'common/extensions/api/api.gyp:api',

[battre, 2012/02/20 10:17:36]

Why is this necessary? should this not be inherited from browser?

Without this, the compiler does not find the generated include files:

../../chrome/browser/extensions/api/declarative/rules_registry.h:12:67: error:
chrome/common/extensions/api/experimental.declarative.h: No such file or
directory

[not at google - send to devlin, 2012/02/20 11:50:51]

Hm. Damn, we will need to look into that, but it's probably to do with the way
that include paths are set up... the .h files get generated to some intermediate
build directory and possibly that's only visible during the "chrome" compile
stage, so it doesn't get shared.

It actually looks like protobuf compilation has the same problem (2 lines
above), which is interesting because it's what we based the gyp stuff on.

Chris, any idea?

         'renderer',
         'test_support_common',
         '../base/base.gyp:base',