My local node `master` branch build (V8 6.4.388-40) does have a large
libv8_base.a, but the final binary is small. Maybe the compilers are
putting more stuff in there that the linker strips out.

❯ ls -l ./out/Release/libv8_base.a
-rw-r--r--  1 ofrobots  eng  1269949240 Feb  7 08:14
./out/Release/libv8_base.a

❯ ls -l out/Release/node
-rwxr-xr-x  1 ofrobots  eng  36398764 Feb  7 08:14 out/Release/node


On Wed, Feb 7, 2018 at 4:25 PM Jakob Kummerow <jkumme...@chromium.org>
wrote:

> That does indeed seem very large. On Linux with a current checkout (and
> without v8_static_library=true), my out/x64.release/obj/v8_base directory
> with all the .o files is only 29MB.
>
> Unfortunately, I have no idea what might be causing the difference in your
> case. Do any *.o files stand out as very big? Have you tried deleting the
> output directory (remember to save your args.gn first!) and compiling
> everything from scratch? It's a blunt instrument but sometimes helps get
> rid of old cruft...
>
>
> On Wed, Feb 7, 2018 at 3:58 PM Ryan Dahl <r...@tinyclouds.org> wrote:
>
>> Hi,
>>
>> I've noticed that the build size in the latest V8 releases is very large.
>>
>> For example, on 6.5.257, I get
>>
>> -rw-r--r--  1 rld  staff   1.1G Feb  7 18:49 out/v8build/obj//libv8_base.a
>>
>> It's similarly large on 6.6.164. I'm experiencing this on OSX and here is
>> the configuration I'm using:
>>
>>     is_component_build=false
>>     is_debug=false
>>     v8_deprecation_warnings=true
>>     v8_enable_gdbjit=false
>>     v8_enable_i18n_support=false
>>     v8_experimental_extra_library_files=[]
>>     v8_extra_library_files=[]
>>     v8_imminent_deprecation_warnings=true
>>     v8_static_library=true
>>     v8_target_cpu="x64"
>>     v8_untrusted_code_mitigations=false
>>     v8_use_external_startup_data=false
>>     v8_use_snapshot=false
>>
>> Any suggestions on how to reduce the size? I'm surprised that the build
>> size has gone from under 100M to over 1G in the span of a few years - is
>> this a bug on my end or working as intended?
>>
>>
>> Thanks,
>> Ryan
>>
>>
>> --
>> --
>> 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.
>>
> --
> --
> 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.
>

-- 
-- 
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.

Reply via email to