Do not try to link chrome or app_shell in chromeos gn build.

Do not try to link chrome or app_shell in chromeos gn build.

On ChromeOS, Chrome links in the remoting host, which isn't gn-ified yet.
I'm not quite sure why app_shell doesn't work, but it might be the same
issue.

TBR=cmasone@chromium.org
BUG=424337
Committed: https://crrev.com/6fc75b3f8718593090cca2b4a6cba0e84122d201
Cr-Commit-Position: refs/heads/master@{#302524}

[Dirk Pranke, 2014-11-03 22:44:53]

The CQ bit was checked by dpranke@chromium.org

[commit-bot: I haz the power, 2014-11-03 22:46:39]

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

[Dirk Pranke, 2014-11-03 22:50:02]

The CQ bit was checked by dpranke@chromium.org

[commit-bot: I haz the power, 2014-11-03 22:50:42]

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

[Chris Masone, 2014-11-03 22:57:52]

If this is preferred place to do this, as opposed to in bot configs, then LGTM

[Dirk Pranke, 2014-11-03 22:59:20]

On 2014/11/03 22:57:52, Chris Masone wrote:
> If this is preferred place to do this, as opposed to in bot configs, then LGTM

It is, yes :).

Ultimately, when we are also running tests, the list of targets should be
determined by which tests we want to run (which is also drawn from a file in the
source tree), but using "all" and having all be defined by the GN files
themselves is a good intermediate option.

[commit-bot: I haz the power, 2014-11-04 00:04:11]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2014-11-04 00:04:48]

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