Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code

Unified Diff: README.md

Issue 29557565: Issue 5800 - Add option to specify a list of V8 libraries (Closed)
Patch Set: Supporting multiple libraries Created Sept. 27, 2017, 12:13 p.m.
Use n/p to move between diff chunks; N/P to move between comments.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | libadblockplus-android/jni/Android.mk » ('j') | libadblockplus-android/jni/Android.mk » ('J')
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: README.md
diff --git a/README.md b/README.md
index deb034f259aff3b9cb296db73abe1b8a96308ea1..7c490526b4f7a2361f62dd902274c5d6caaf1490 100644
--- a/README.md
+++ b/README.md
@@ -91,6 +91,29 @@ An app that uses the library have to add the following permissions to `AndroidMa
(added automatically if building with Gradle or should be added manually otherwise).
+### Building with prebuilt shared V8
+
+This can be desired to use product's V8 (let's say Chromium) instead of libadblockplus built-in V8.
+Put prebuilt shared V8 library file(s) in ARCH directories and set `SHARED_V8_LIB_FILENAME`
+environment variable before building. You can pass multiple filenames, separated with `:`.
+Libadblockplus is required to be linked with that library file(s).
+
+For example (build with Gradle):
+
+ SHARED_V8_LIB_FILENAME=libv8.cr.so ./gradlew clean assemble
+
+or
+
+ SHARED_V8_LIB_FILENAME=libv8.cr.so:libfoo.so ./gradlew clean assemble
+
+for multiple library files.
+
+Note
+
+ [Configuration] Linking dynamically with shared v8 library ./libadblockplus-binaries/android_armeabi-v7a/libv8.cr.so
+
+output while building native library.
+
## Library tests
Android tests for the library.
« no previous file with comments | « no previous file | libadblockplus-android/jni/Android.mk » ('j') | libadblockplus-android/jni/Android.mk » ('J')

Powered by Google App Engine
This is Rietveld