Upstream Android's PathUtils implementation.

base/base.gyp

Index: base/base.gyp
diff --git a/base/base.gyp b/base/base.gyp
index d34476b0ef0cf62191d49a38962a594ff38d51dc..d3b64eb8a0a853adfc15ee72ca7aed4c5a7b2cc8 100644
--- a/base/base.gyp
+++ b/base/base.gyp
@@ -115,6 +115,29 @@
       ],
     },
     {
+      'target_name': 'base_jni_headers',

[Mark Mentovai, 2012/02/23 18:43:33]

If we need to do this in many locations, we may want to provide a template to
deal with it.

+      'type': 'none',
+      'actions': [
+        {
+          'action_name': 'generate_jni_headers',
+          'inputs': [
+            'android/jni_generator/jni_generator.py',
+            'android/java/PathUtils.java',
+          ],
+          'outputs': [
+            '<(SHARED_INTERMEDIATE_DIR)/base/jni/path_utils_jni.h',
+          ],
+          'action': [
+            'python',
+            'android/jni_generator/jni_generator.py',
+            '-o',

[Mark Mentovai, 2012/02/23 18:43:33]

Is this the right way to invoke jni_generator.py?

[Peter Beverloo, 2012/02/29 15:40:22]

Yes (per a chat with bulach@). This is used to prevent rebuilding headers when
it's not necessary, and the argument is trimmed off the output files as expected
on line 961 of jni_generator.py.

+            '<@(_inputs)',

[Mark Mentovai, 2012/02/23 18:43:33]

This will expand to all of the inputs, including jni_generator.py. Do you want
that?

+            '<@(_outputs)',
+          ],
+        }
+      ],
+    },
+    {
       'target_name': 'base_unittests',
       'type': 'executable',
       'sources': [