Move json schema compiler target into build/ to match gyp

Move json schema compiler target into build/ to match gyp

ui/ and chrome/ should not depend on anything from //extensions.

R=brettw@chromium.org

Committed: https://crrev.com/145636c494aa8b2ea39eb86f1b9c13f9ee52f3f7
Cr-Commit-Position: refs/heads/master@{#297528}

[brettw, 2014-09-23 21:42:57]

Too bad, I liked it in extensions...

https://codereview.chromium.org/597713002/diff/1/ui/accessibility/BUILD.gn
File ui/accessibility/BUILD.gn (right):

https://codereview.chromium.org/597713002/diff/1/ui/accessibility/BUILD.gn#ne...
ui/accessibility/BUILD.gn:74: json_schema_compile("ax_gen") {
I wonder if we should pick a different name. I recall that the GYP one has
separate steps for compile and bundle, while the GN template does both. maybe
"json_schema_api"?

[jamesr, 2014-09-24 00:23:40]

Sure, PTAL

[brettw, 2014-09-24 00:33:50]

lgtm

[jamesr, 2014-09-29 22:22:01]

The CQ bit was checked by jamesr@chromium.org

[commit-bot: I haz the power, 2014-09-29 22:23:08]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/597713002/60001

[commit-bot: I haz the power, 2014-09-29 22:32:58]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-09-29 22:32:59]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[commit-bot: I haz the power, 2014-09-30 22:28:16]

Patchset 4 (id:??) landed as
https://crrev.com/145636c494aa8b2ea39eb86f1b9c13f9ee52f3f7
Cr-Commit-Position: refs/heads/master@{#297528}

[jamesr, 2014-09-30 22:28:17]

Committed patchset #4 (id:60001) manually as
145636c494aa8b2ea39eb86f1b9c13f9ee52f3f7.