Android: Add chrome-specific dynamic linker.

content/content.gyp

Index: content/content.gyp
diff --git a/content/content.gyp b/content/content.gyp
index 221a1a53928a3e57c7edc508631022819b66a135..88d10b061ca211b11f6bce2d78f444fdfd731abf 100644
--- a/content/content.gyp
+++ b/content/content.gyp
@@ -494,6 +494,28 @@
           },
           'includes': [ 'content_jni.gypi' ],
         },
+        {
+          'target_name': 'content_android_linker',
+          'type': 'shared_library',
+          'conditions': [
+            ['android_webview_build == 0', {
+              # Avoid breaking the webview build because it doesn't have
+              # <(android_ndk_root)/crazy_linker.gyp. Note that it never uses
+              # the linker anyway.
+              'sources': [
+                'common/android/linker/linker_jni.cc',
+              ],
+              'dependencies': [
+                '<(android_ndk_root)/crazy_linker.gyp:crazy_linker',
+              ],
+              'include_dirs': [
+                # This is necessary to include base/android/sys_utils_constants.h

[jochen (gone - plz use gerrit), 2013/10/09 12:08:23]

shouldn't you depend on the target that has this header if you use it?

[digit1, 2013/10/09 13:33:49]

Actually no, it's a very special case: the header needs to be included to get a
constant value that is being used in a source file that _cannot_ depend on base/
at all. See the comments in sys_utils_constants.h and in linker_jni.cc

I've made the comment more explicit about this.

[jochen (gone - plz use gerrit), 2013/10/10 11:39:29]

I'd either put this into a gyp variable, or introduce a new base target that is
safe to depend on.

[digit1, 2013/10/10 12:21:41]

Ok, I have added build/android/low_memory_device.gypi to address this. Now I
need a base/ reviewer though :-)

thakis, could you look at the latest change in base/base.gypi?

+                '..',
+              ],
+            }],
+          ],
+        },
+
       ],
     }],  # OS == "android"
   ],