Make it possible to use OSMesa on Android

content/content_shell.gypi

Index: content/content_shell.gypi
diff --git a/content/content_shell.gypi b/content/content_shell.gypi
index 0895c2c7e230bacd8d77e95ed5b1350e407f9228..ef564525601622a6ef0f96a4a4ca524132e9208b 100644
--- a/content/content_shell.gypi
+++ b/content/content_shell.gypi
@@ -841,6 +841,7 @@
             '../base/base.gyp:base_java',
             '../media/media.gyp:media_java',
             '../net/net.gyp:net_java',
+            '../third_party/mesa/mesa.gyp:osmesa',
             '../tools/android/forwarder/forwarder.gyp:forwarder',
             '../ui/ui.gyp:ui_java',
           ],
@@ -852,7 +853,24 @@
             'native_lib_target': 'libcontent_shell_content_view',
             'additional_input_paths': ['<(PRODUCT_DIR)/content_shell/assets/content_shell.pak'],
             'asset_location': '<(ant_build_out)/content_shell/assets',
+            'extra_native_libs': ['<(SHARED_LIB_DIR)/libosmesa.so'],
           },
+          'actions': [
+            {

[no sievers, 2013/11/11 20:20:05]

Can this somehow move to the libosmesa target itself or to its own target?

Other targets might need this too, and it creates a gyp warning if I simply
duplicate it for other targets.

+              # Copy libosmesa.so to the out/$BUILDTYPE/lib/ directory. The
+              # write_ordered_libraries.py script requires it to be in that
+              # directory, because otherwise it will be seen as a system lib
+              # which causes it to not be stripped.
+              'action_name': 'copy_libosmesa',
+              'inputs': ['<(PRODUCT_DIR)/libosmesa.so'],
+              'outputs': ['<(SHARED_LIB_DIR)/libosmesa.so'],
+              'action': [
+                'cp',
+                '<(PRODUCT_DIR)/libosmesa.so',
+                '<(SHARED_LIB_DIR)/libosmesa.so',
+              ],
+            },
+          ],
           'conditions': [
             ['android_webview_build==0', {
               'dependencies': [