Issue 6750 - Update libadblockplus dependency to revision hg:4f6413dbcf2e

README.md

Index: README.md
diff --git a/README.md b/README.md
index ef024ba90c553ef4034d31409d54f672a5da5b2c..3a3e5405a528caa44d0e64aebbf7f54b7ad1ce3b 100644
--- a/README.md
+++ b/README.md
@@ -25,6 +25,20 @@ You can find it in the 'adblock-android' directory.
 
 Edit 'buildToolsVersion' in 'build.gradle' files if necessary.
 
+#### Building of libadblockplus
+
+First, we need to build `V8` required for `libadblockplus`.

[sergei, 2018/06/22 09:21:16]

Perhaps later we could incorporate either in libabp or in gradle the
functionality which can guess whether the V8 should be fetched and does it. So,
in order to build it, one has to merely run one command ./gradlew
assembleRelease or its moral equivalent.

[anton, 2018/06/22 10:58:18]

"proper" way would be to compile `libadblockplus` as gradle/maven module, push
it to some public repository and add dependency to the module and let gralde
download it automatically. This should be done while building of
`libadblockplus`.

+See `libadblockplus/README` or V8 documentation on how to build V8 or
+fetch precompiled one. Run in 'libadblockplus' directory:

[sergei, 2018/06/22 09:21:16]

I would say, "For the latter, run in 'libad...."

[anton, 2018/06/22 10:58:18]

Acknowledged.

+
+    make TARGET_OS=android ABP_TARGET_ARCH=arm Configuration=release get-prebuilt-v8
+    make TARGET_OS=android ABP_TARGET_ARCH=ia32 Configuration=release get-prebuilt-v8

[sergei, 2018/06/22 09:21:16]

what about arm64?

[anton, 2018/06/22 10:58:17]

It's not yet supported.

+
+Then we can build `libadblockplus`:
+
+    make TARGET_OS=android ABP_TARGET_ARCH=arm Configuration=release
+    make TARGET_OS=android ABP_TARGET_ARCH=ia32 Configuration=release
+
 #### Building from command-line
 
 In the project root directory create the file _local.properties_ and set
@@ -65,16 +79,17 @@ output while building
 
 This can be desired to use product's V8 (let's say Chromium) instead of built-in V8.
 Put prebuilt shared V8 library file(s) in ARCH directories and set `SHARED_V8_LIB_FILENAMES`
-environment variable before building. You can pass multiple filenames, separated with space.
+environment variable and `SHARED_V8_LIB_DIR` before building.
+You can pass multiple filenames in `SHARED_V8_LIB_FILENAMES`, separated with space.
 Libadblockplus is required to be linked with that library file(s).
 
 For example:
 
-    SHARED_V8_LIB_FILENAMES=libv8.cr.so ./gradlew clean assemble
+    SHARED_V8_LIB_FILENAMES=libv8.cr.so SHARED_V8_LIB_DIR="/tmp/shared_v8" ./gradlew clean assembleAbi_arm
     
 or
 
-    SHARED_V8_LIB_FILENAMES="libv8.cr.so libfoo.so" ./gradlew clean assemble
+    SHARED_V8_LIB_FILENAMES="libv8.cr.so libv8_libbase.cr.so libv8_libplatform.cr.so" SHARED_V8_LIB_DIR="/tmp/shared_v8" ./gradlew clean assembleAbi_arm
     
 for multiple library files.
 
@@ -82,14 +97,11 @@ Note
   
     [Configuration] Excluding shared v8 library libv8.cr.so from AAR
     ...
-    [Configuration] Linking dynamically with shared v8 library ./libadblockplus-binaries/android_armeabi-v7a/libv8.cr.so
+    [Configuration] Linking dynamically with shared v8 library /tmp/shared_v8/release/libv8.cr.so
     ...
 
 output while building.
 
-Set `SHARED_V8_LIB_DIR` environment variable as full absolute path to pass
-specific directory instead of default one (`adblock-android/jni/libadblockplus-binaries`).
-
 ### Building for single ARCH
 
 By default adblock-android is built for both ARM and x86 and it can be filtered when