Changes between Version 1 and Version 2 of Ticket #6529


Ignore:
Timestamp:
03/27/2018 01:15:28 PM (22 months ago)
Author:
sergz
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #6529 – Description

    v1 v2  
    22libadlockplus requires V8 to run JS. We do provide precompiled V8 in libadblockplus-binaries for libadblockplus-android to link it as shared library (libadblockplus-jni.so). For this we don't have to update V8 - it just works. 
    33 
    4 But for using libadblockplus + libadblockplus-android in Chromium with Chromium's V8 we have to make sure we can use Chromium's V8 (sometimes significant changes are done, e.g. changing Android NDK version). But we may want to avoid updating it every time it's changed in Chromium and having both V8 in the final apk. This obviously increases the final apk size but helps to reduce the amount of work required to migrate libadblockplus + libadblockplus-android to V8 version, which is used in Chromium, thus it helps to reduce the time needed to update libadblockplus + libadblockplus-android in Chromium. 
     4But for using libadblockplus + libadblockplus-android in Chromium with Chromium's V8 we have to make sure we can use Chromium's V8 (sometimes significant changes are done, e.g. changing Android NDK version). But we may want to avoid updating it every time it's changed in Chromium and having both V8 in the final apk. This obviously increases the final apk size but helps to reduce the amount of work required to either update Chromium with V8 or integrated adblockplus. In the former one has to basically do nothing in order to migrate libadblockplus + libadblockplus-android into newer Chromium. In the latter it helps to reduce the time needed to update libadblockplus + libadblockplus-android in Chromium. 
    55 
    66Sergei is 90% sure both V8 can live together in the same Chromium process if our V8 is statically linked with our ''.so'' file.