win: Call clang-cl instead of clang-cl.exe when targeting win on a non-win host.

win: Call clang-cl instead of clang-cl.exe when targeting win on a non-win host.

No behavior change, since non-win hosts targeting windows currently don't
exist. But if they did, there are three choices for how to invoke the compiler:

1. Call the compiler on the host clang-cl.exe instead of clang-cl.  That's weird
   because clang-cl is a host-native binary.

2. Don't append ".exe" to any program in build/toolchain/win/BUILD.gn -- it's
   probably not needed on Windows.  But if we end up running real Windows
   binaries on non-Windows (e.g. midl.exe through wine), then those would
   have a .exe extension on the non-Windows host.

3. Do what this CL does. This seems nicest.

BUG=495204
Committed: https://crrev.com/8391051c80fa58d3b4a9021f4185cbc71e69f32e
Cr-Commit-Position: refs/heads/master@{#369854}

[Nico, 2016-01-15 01:00:04]

thakis@chromium.org changed reviewers:
+ brettw@chromium.org

[Nico, 2016-01-15 01:00:04]

((The motivation here is upstreaming easy changes from my
build-chrome-win-on-mac branch)

[brettw, 2016-01-15 21:19:55]

lgtm

[Nico, 2016-01-15 21:22:30]

The CQ bit was checked by thakis@chromium.org

[commit-bot: I haz the power, 2016-01-15 21:23:53]

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

[commit-bot: I haz the power, 2016-01-15 21:52:14]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-01-15 21:53:20]

Description was changed from

==========
win: Call clang-cl instead of clang-cl.exe when targeting win on a non-win host.

No behavior change, since non-win hosts targeting windows currently don't
exist. But if they did, there are three choices for how to invoke the compiler:

1. Call the compiler on the host clang-cl.exe instead of clang-cl.  That's weird
   because clang-cl is a host-native binary.

2. Don't append ".exe" to any program in build/toolchain/win/BUILD.gn -- it's
   probably not needed on Windows.  But if we end up running real Windows
   binaries on non-Windows (e.g. midl.exe through wine), then those would
   have a .exe extension on the non-Windows host.

3. Do what this CL does. This seems nicest.

BUG=495204
==========

to

==========
win: Call clang-cl instead of clang-cl.exe when targeting win on a non-win host.

No behavior change, since non-win hosts targeting windows currently don't
exist. But if they did, there are three choices for how to invoke the compiler:

1. Call the compiler on the host clang-cl.exe instead of clang-cl.  That's weird
   because clang-cl is a host-native binary.

2. Don't append ".exe" to any program in build/toolchain/win/BUILD.gn -- it's
   probably not needed on Windows.  But if we end up running real Windows
   binaries on non-Windows (e.g. midl.exe through wine), then those would
   have a .exe extension on the non-Windows host.

3. Do what this CL does. This seems nicest.

BUG=495204

Committed: https://crrev.com/8391051c80fa58d3b4a9021f4185cbc71e69f32e
Cr-Commit-Position: refs/heads/master@{#369854}
==========

[commit-bot: I haz the power, 2016-01-15 21:53:20]

Patchset 1 (id:??) landed as
https://crrev.com/8391051c80fa58d3b4a9021f4185cbc71e69f32e
Cr-Commit-Position: refs/heads/master@{#369854}