You might be able to shave off another couple of kilobytes by using the 
interpreted regexp engine by compiling with regexp=interpreted. If you use 
V8 3.25 or older, you may also remove the debugger by debuggersupport=off. 
Older V8 would also have fewer features, thereby reducing the binary size. 
Notable features are ES6 language features and Turbo-fan, the new compiler 
which is not even used by default at the moment.

Yang


On Friday, August 29, 2014 12:04:57 AM UTC+2, Matt Kline wrote:
>
> d8 comes out to about 4 MB, so the final executable size should be fine. 
> The .lib size is somewhat important, however, as the powers that be have 
> decided that the .lib files will be placed in the Git repo of the project 
> using them. Because Git handles large files rather poorly, and because 
> Github (who we are using for hosting) places restrictions on file size, I 
> would like to make the .lib files as small as possible too.
>
> On Thursday, August 28, 2014 11:52:44 AM UTC-7, Ben Noordhuis wrote:
>>
>> On Thu, Aug 28, 2014 at 7:30 PM, Matt Kline <[email protected]> wrote: 
>> > Thank you! By disabling i18n and stripping it, I was able to get the 
>> build 
>> > down to 2.8 MB. This is excellent. 
>> > 
>> > Now, how would I pull a similar stunt on Windows? As mentioned 
>> previously, I 
>> > was able to reduce v8_base.lib to about 38 MB by setting "Debug 
>> Information 
>> > Format" to "None" and optimization flags to "Minimum Size" (/O1) and 
>> "Favor 
>> > small code" (/Os), but that's still massive, and that's just one of the 
>> > files. 
>>
>> I'm not sure if you should be looking at the *.lib file, it probably 
>> contains a lot of metadata that doesn't end up in the final 
>> executable.  How big is a statically linked d8.exe? 
>>
>

-- 
-- 
v8-users mailing list
[email protected]
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to