Changes between Initial Version and Version 1 of Ticket #6529


Ignore:
Timestamp:
03/27/2018 01:03:21 PM (2 years ago)
Author:
sergz
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #6529 – Description

    initial v1  
    11=== Background === 
    2 libadlockplus requires V8 to run JS. Do we provide precompiled V8 in libadblockplus-binaries for libadblockplus-android to compile it as shared library (libadblockplus-jni.so). For this we don't have to update V8 - it just works. 
     2libadlockplus 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, eg. changin Android NDK version). But we may want to avoid updating it every time it's changed in Chromium and having both V8 in final apk. This obviously increases final apk size but helps to reduce work amount required to migrate in libadblockplus + libadblockplus-android to V8 version used 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 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. 
    55 
    6 Sergei is 90% sure they can live together in same Chromium process. 
     6Sergei is 90% sure both V8 can live together in the same Chromium process if our V8 is statically linked with our ''.so'' file. 
    77 
    88=== What to do === 
    9 We need to link libadblockplus-android with prebuilt V8 from -binaries (statically) and make sure we can work with it in Chromium context (having both Chromium V8 and libadblockplus prebuilt V8). 
     9We need to link libadblockplus-android with prebuilt V8 from -binaries (statically) and ensure (check) that it can work in Chromium context (having both Chromium V8 and libadblockplus prebuilt V8).