Excuse me? On Windows, "C:\Program Files (x86)\Google\Chrome" takes 603 MiB only — and it contains a 295 MiB file called "chrome.7z" inside an "Installer" subdirectory. What does Linux distribution contains that takes the rest of the space?
That's not the Linux distribution, it's the source code. Straight from Google.
https://commondatastorage.googleapis.com/chromium-browser-of...
The compiled binary is much smaller:
~ $ du -h /usr/lib64/chromium-browser
16K /usr/lib64/chromium-browser/MEIPreload
360K /usr/lib64/chromium-browser/locales
383M /usr/lib64/chromium-browserHuh, so the size comparison actually goes "compiled binary" < "debug symbols" < "source code", interesting to know, thanks.
Debug symbols are often larger than the original source code though. The main culprit is C++ template expansions, which can get crazy long.
Re:When Debug Symbols Get Large
by LanternLight83 on Thursday March 09, 2023 @03:23PM
(#35086165)
Love the use of distfiles for an in the spot demonstration, makes me miss Gentoo. I suppose functional package-manager users have similar files in their stores. Thanks for sharing.
Debug symbols in general tend to be very big. You need to be able to map each instruction in the binary to a line of code. You can expect a compiler to break each line of code into several instructions, and you can also expect that the instructions are out of order and interleaved with neighboring lines of code. So each instruction will need its own unique entry.
> I am willing to bet that the executable and the source code combined together would take less space,