GN: Get //chrome/* mostly working on android

GN: Get //chrome/* mostly working on android

This gets the //chrome subtree down to a fairly small number of build
errors on Android. Most of the changes are making features not enabled
on android like extensions and plugins properly guarded. This also adds
a few jni targets and fixes up some bitrotted bits.

R=brettw@chromium.org, cjhopman@chromium.org

Committed: https://chromium.googlesource.com/chromium/src/+/2ed4d695d6cf2917fc0e52f767d629fbefa7a1f9

[jamesr, 2014-09-15 05:50:22]

Remaining issues are some resources things I don't understand and some include
path shenanagins in //chrome/browser that are pretty hard to understand in the
GYP build.  I still think this is a useful checkpoint.

https://codereview.chromium.org/571863002/diff/1/chrome/browser/BUILD.gn
File chrome/browser/BUILD.gn (right):

https://codereview.chromium.org/571863002/diff/1/chrome/browser/BUILD.gn#newc...
chrome/browser/BUILD.gn:10: # produces a conflict for the "grit" template so we
have to only include one.
this doesn't seem right, but it's needed to build. is this how imports are
expected to interact?

[cjhopman, 2014-09-15 17:23:07]

cjhopman@chromium.org changed reviewers:
+ cjhopman@chromium.org

[cjhopman, 2014-09-15 17:23:08]

https://codereview.chromium.org/571863002/diff/1/chrome/browser/BUILD.gn
File chrome/browser/BUILD.gn (right):

https://codereview.chromium.org/571863002/diff/1/chrome/browser/BUILD.gn#newc...
chrome/browser/BUILD.gn:10: # produces a conflict for the "grit" template so we
have to only include one.
On 2014/09/15 05:50:22, jamesr wrote:
> this doesn't seem right, but it's needed to build. is this how imports are
> expected to interact?

I had to do the same thing in //net. I definitely consider this a bug (I filed
http://crbug.com/393704 a while ago).

[brettw, 2014-09-15 18:11:10]

https://codereview.chromium.org/571863002/diff/1/chrome/browser/BUILD.gn
File chrome/browser/BUILD.gn (right):

https://codereview.chromium.org/571863002/diff/1/chrome/browser/BUILD.gn#newc...
chrome/browser/BUILD.gn:10: # produces a conflict for the "grit" template so we
have to only include one.
This is already fixed but I haven't pushed the new binary yet.

[brettw, 2014-09-15 18:13:29]

lgtm

[cjhopman, 2014-09-15 21:55:13]

lgtm

[jamesr, 2014-09-16 00:26:02]

The CQ bit was checked by jamesr@chromium.org

[commit-bot: I haz the power, 2014-09-16 00:37:45]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patchset/571863002/1

[commit-bot: I haz the power, 2014-09-16 01:20:36]

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

[commit-bot: I haz the power, 2014-09-16 01:20:37]

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

[jamesr, 2014-09-17 01:26:47]

The CQ bit was checked by jamesr@chromium.org

[commit-bot: I haz the power, 2014-09-17 01:26:59]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patchset/571863002/20001

[commit-bot: I haz the power, 2014-09-17 01:38:54]

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

[commit-bot: I haz the power, 2014-09-17 01:38:56]

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-17 05:22:01]

Patchset 2 (id:??) landed as
https://crrev.com/2ed4d695d6cf2917fc0e52f767d629fbefa7a1f9
Cr-Commit-Position: refs/heads/master@{#295231}

[jamesr, 2014-09-17 05:22:03]

Committed patchset #2 (id:20001) manually as 2ed4d69.