Android build target for libadblockplus

libadblockplus.gyp

Index: libadblockplus.gyp
===================================================================
--- a/libadblockplus.gyp
+++ b/libadblockplus.gyp
@@ -22,7 +22,12 @@
       'include',
       'third_party/v8/include'
     ],
-    'dependencies': ['third_party/v8/tools/gyp/v8.gyp:v8'],
+    'dependencies': [],

[Wladimir Palant, 2013/05/07 08:18:54]

You can simply remove that entry, having an empty list here is pointless.

+    'conditions': [
+      ['OS!="android"', {
+        'dependencies': ['third_party/v8/tools/gyp/v8.gyp:v8'],

[Eric, 2013/06/12 14:48:17]

I am curious as to why this dependency is needed for android but not the other
platforms. Any insight?

[Wladimir Palant, 2013/06/12 19:33:23]

It's actually the other way round. For Android we have to build V8 separately
and merely use the already compiled libs here because V8 uses a huge makefile
for the build that calls gyp as the last step. To build V8 along with our code
we would need to duplicate everything in that makefile which is clearly not a
good idea.

+      }]
+    ],
     'sources': [
       'src/AppInfoJsObject.cpp',
       'src/ConsoleJsObject.cpp',
@@ -42,7 +47,12 @@
     'direct_dependent_settings': {
       'include_dirs': ['include']
     },
-    'export_dependent_settings': ['third_party/v8/tools/gyp/v8.gyp:v8'],
+    'export_dependent_settings': [],

[Wladimir Palant, 2013/05/07 08:18:54]

You can simply remove that entry, having an empty list here is pointless.

+    'conditions': [
+      ['OS!="android"', {
+        'export_dependent_settings': ['third_party/v8/tools/gyp/v8.gyp:v8'],
+      }]
+    ],
     'conditions': [
       ['have_curl==1',
         {