Chromium mini安装程序大小达到1.19GB? [英] Chromium mini installer size reaches 1.19GB?

问题描述

我正在研究铬，并成功运行以下命令:

I am working on chromium and after successfully running the command:

ninja -C out\BuildFolder mini_installer

我在生成目录中获得mini_installer.exe，但问题是mini_installer.exe的大小达到1.19 GB.我不明白怎么了?任何帮助将不胜感激.

I get mini_installer.exe in the build directory, but the issue is that the mini_installer.exe size reaches 1.19 GB. I couldn't understand what's wrong? Any help would be appreciated.

推荐答案

最有可能是小型安装程序的调试版本.您可以修改 args.gn 的内容以配置调试/发行版本，删除/添加某些功能，从某些库中删除调试符号等.例如， args中的以下GN参数.gn 文件可用于生成优化的64位小型安装程序:

It's most likely a debug version of mini installer. You can modify the contents of args.gn to configure debug/release version, remove/add certain features, remove debug symbols from certain libraries etc. For example, the following GN arguments in args.gn file can be used to generate an optimized 64-bit mini installer:

is_debug = false

target_cpu = "x64" # x86 for 32-bit

remove_webcore_debug_symbols = true

is_official_build = true

如果您没有调试Webcore的计划，则应将 remove_webcore_debug_symbols 设置为 true ，因为这会减小小型安装程序的大小.同时设置 symbol_level = 0 应该会使小型安装程序变得更小，但是请记住，由于没有调试符号和高度优化的可执行文件，这样做将几乎使调试Chromium fork成为不可能.另外，对于调试版本，应将 is_component_build = true 设置为启用更快的链接，但对于发行版本，则应将其值设置为 false 以最大程度地减少已编译可执行文件的大小.还要减小小型安装程序的大小.

If you have no plan to debug webcore then you should set remove_webcore_debug_symbols to true, as it will reduce the size of mini installer. Also setting the symbol_level = 0 should make even smaller mini installer but remember, doing so will make debugging your Chromium fork almost impossible because of no debug symbols and highly optimized executable file. Also, for debug versions you should set is_component_build = true to enable faster linking but you should set its value to false for release builds to minimize the size of compiled executables, which will reduce the size of mini installer too.

这篇关于Chromium mini安装程序大小达到1.19GB?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！