I have a similar issue with Windows libraries in v6.9 and newer. I'm still looking for an answer, too.
https://groups.google.com/forum/#!topic/v8-users/P5dHmxNm-TY --Terry On Thursday, July 19, 2018 at 1:33:03 AM UTC-7, YJ wrote: > > hi all, > > I am using the following gn args for x64 > > is_debug = false >> target_cpu = "x64" >> use_drfuzz = false >> use_libfuzzer = false >> v8_enable_test_features = "" >> v8_experimental_extra_library_files = [] >> v8_extra_library_files = [] >> symbol_level = 1 >> is_component_build = false >> use_sysroot = false >> use_glib = false >> use_custom_libcxx = false >> use_custom_libcxx_for_host = false >> v8_enable_i18n_support = false >> v8_static_library = true > > > They worked fine until version 6.5. > > With 6.7 and 6.8, things work normally on macOS, but with linux the built > libs are no longer fully static. For example, the size of libv8_base.a used > to be 80+MB, now it is only a bit over 2MB. These libraries can be linked > okay but they are not truly static. If they are moved to a different > location they are no longer usable. > > Does anyone know what has changed regarding this ? > -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
