Allow the mojo shell to run on android.

mojo/mojo.gyp

Index: mojo/mojo.gyp
diff --git a/mojo/mojo.gyp b/mojo/mojo.gyp
index 5621bea4f359611d22e426a73795951cfe97d0cf..85c1740d166a0e211968e3643c5140342e025847 100644
--- a/mojo/mojo.gyp
+++ b/mojo/mojo.gyp
@@ -866,6 +866,9 @@
             'java_in_dir': '<(DEPTH)/mojo/shell/android/apk',
             'resource_dir': '<(DEPTH)/mojo/shell/android/apk/res',
             'native_lib_target': 'libmojo_shell',
+            'additional_bundled_libs': [
+              '<(SHARED_LIB_DIR)/libmojo_network_service.>(android_product_extension)',

[tim (not reviewing), 2014/06/26 16:33:02]

q's mostly for my own education:
- What's "android_product_extension"?
- How come the native_viewport service and network_service dependencies are so
different?

[qsr, 2014/06/26 16:41:16]

android_product_extension is .so for normal build, .cr.so for component build,
see: build/common.gypi for explanations.

The native_viewport_service is run by the shell itself (see
mojo/shell/context.cc), which the network service is a normal application
(loaded from a .so, in another process if the shell is multi-process), but that
is special in the sense that this it is hardcoded has being a local application
that you load from disk, and that will then receive network request allowing you
to download other applications.

+            ],
           },
           'includes': [ '../build/java_apk.gypi' ],
         }