On Fri, May 12, 2017 at 12:07 PM, <[email protected]> wrote: > We are working on the V8 version 5.3.332 & we choose to compile it as static > library. We compiled the library with the following configuration. > > MAKE_TARGET="android_$BUILD_LIB_VERSION.$BUILD_MODE" > make $MAKE_TARGET -j1 snapshot=off debuggersupport=off > GYPFLAGS="-Dandroid_ndk_root=$NDK_DIR -Dv8_use_snapshot='false' > -Dv8_enable_i18n_support=0" ANDROID_NDK_ROOT=$NDK_DIR > > With the above configuration, release version of libv8_base.a is around 35MB > in size. So my question is, is V8 expected to be 35MB in size with i18n & > snapshot support off ? > is there any additional flags which help us to get the v8 size reduced > further ? > > One more observation is, even if we pass debuggersupport=off , we are still > able to build & debug my JS app. So our expectation here is, debug API's > would be stripped off from library and no more runtime JS debug support > available. > Please correct if we are not passing the build configuration properly & > suggest .
debuggersupport=off was removed in 2014, debug support is unconditionally enabled nowadays. 35 MB for the archive doesn't seem out of the ordinary but a lot of that is probably DWARF debug info. Link it and strip the binary (with strip(1)), that should give a better picture of its real size. -- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
