Adding app_shim executable on Windows.

chrome/app_shim/app_shim_win.gypi

Index: chrome/app_shim/app_shim_win.gypi
diff --git a/chrome/app_shim/app_shim_win.gypi b/chrome/app_shim/app_shim_win.gypi
new file mode 100644
index 0000000000000000000000000000000000000000..59391058c2e126e16c60c386debb1a5e9b5594e1
--- /dev/null
+++ b/chrome/app_shim/app_shim_win.gypi
@@ -0,0 +1,29 @@
+# Copyright 2014 The Chromium Authors. All rights reserved.
+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+
+{
+  'targets': [
+    # This is the app shim on Windows. It is a small binary that simply runs
+    # Chrome, passing along any command-line arguments.
+    {
+      'target_name': 'win_app_shim',
+      'type': 'executable',
+      'include_dirs': [
+        '../..',
+      ],
+      'dependencies': [
+        '../base/base.gyp:base',
+      ],
+      'sources': [
+        'app_shim_win.cc',
+        'win_app_shim.rc',
+      ],
+      'msvs_settings': {

[jackhou1, 2014/10/26 22:56:09]

The other Windows exe's have a manifest file. I'm not sure if it's essential
though.
https://code.google.com/p/chromium/codesearch#search/&q=exe.manifest&sq=packa...

[robertshield, 2014/10/27 17:30:50]

You  want one to avoid a bunch of shimming that happens if don't have one. This
app is pretty simple today so it might not matter, but to avoid future
headaches, strongly recommend adding one.

[Matt Giuca, 2014/10/30 06:39:05]

OK, I haven't really looked into this. Since it doesn't seem to be necessary
right now, I think I will go ahead without one and look into adding one
alongside the CL where we bundle the exe with Chrome.

What is "shimming" in this context?

[robertshield, 2014/10/31 16:58:30]

API behaviour changes in different OS revisions and Windows uses the
compatibility section of the manifest to figure out which OS version's behaviour
to emulate. One of the emulation mechanisms used is AppCompat which inserts
shims (which are just patches) to preserve old behaviour.

[Matt Giuca, 2014/11/04 04:38:17]

OK, I've added the manifest.

Note: The way the build system is set up, ALL Windows binaries get the standard
compatibility manifest regardless of whether they include their own (so this was
not a concern). But I have added my own manifest that specifies "asInvoked"
(copied from the other manifests around the place).

+        'VCLinkerTool': {
+          'SubSystem': '2',     # Set /SUBSYSTEM:WINDOWS
+        },
+      },
+    },
+  ],  # targets
+}