Add skeleton of content shell for android.

content/shell/android/content_shell.gypi

Index: content/shell/android/content_shell.gypi
diff --git a/content/shell/android/content_shell.gypi b/content/shell/android/content_shell.gypi
new file mode 100644
index 0000000000000000000000000000000000000000..7f87fb32df632e899d39c4eaa7c96bc313444a16
--- /dev/null
+++ b/content/shell/android/content_shell.gypi
@@ -0,0 +1,39 @@
+# Copyright (c) 2012 The Chromium Authors. All rights reserved.

[jam, 2012/03/28 16:23:48]

we should avoid two gypi files with the same name (makes searching hard among
other things).

why are you adding another gypi instead of putting this stuff in
content/content_shell.gypi? all the gypi files in content are in top level

[Satish, 2012/03/28 20:24:49]

Done.

+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+
+{
+  'conditions': [
+    ['OS=="android"', {
+      'targets': [
+        {
+          'target_name': 'content_shell_apk',
+          'message': 'building content shell package',
+          'type': 'none',
+          'actions': [
+            {
+              'action_name': 'content_shell_apk',
+              'inputs': [
+                '<(DEPTH)/content/shell/android/content_shell_apk.xml',
+                '<!@(find shell/android/java -name "*.java")',
+              ],
+              'outputs': [
+                # Awkwardly, we build a Debug APK even when gyp is in
+                # Release mode.  I don't think it matters (e.g. we're
+                # probably happy to not codesign) but naming should be
+                # fixed.
+                '<(PRODUCT_DIR)/ContentShell-debug.apk',
+              ],
+              'action': [
+                'ant',
+                '-DPRODUCT_DIR=<(PRODUCT_DIR)',
+                '-buildfile',
+                '<(DEPTH)/content/shell/android/content_shell_apk.xml',
+              ]
+            }
+          ],
+        },
+      ],
+    }]
+  ]
+}