CODEWITHSUNDEEP
c++google-chromechromium
GAURAV KUMAR JHA
GAURAV KUMAR JHA

Reputation: 190

Chromium mini installer size reaches 1.19GB?

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

ninja -C out\BuildFolder mini_installer

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.

Upvotes: 0

Views: 1389

Answers (1)

Asesh
Asesh

Reputation: 3361

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

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.

Upvotes: 1

Related Questions