Reduce application binary size in debug mode

Asked Jan 25 '22 at 11:36

Active Jan 26 '22 at 09:33

Viewed 486 times

When I compile GTK4 "Hello World" application in rust I get binary with size 192Mb for debug mode. I use old SSD and I worry about it's resource as I compile and debug very frequently. I tried -C prefer-dynamic flag, but size of binary become 188Mb only.

Is this way to make application binary size much smaller?

PS: I work in win10 and use MSYS2. PPS: I don't have problem with release build's size. With -C link-arg=-s and lto = true the size is about 200kb

edited Jan 26 '22 at 09:33

asked Jan 25 '22 at 11:36

ArtDen

1

[This question](https://stackoverflow.com/q/29008127/10113238) might be relevant to you. – smitop Jan 25 '22 at 12:53
@Smitop unfortunately this is not applicable for debug builds. For example adding `-C link-arg=-s` disable ability to debug – ArtDen Jan 25 '22 at 14:32
Debug builds are not meant to be small. Even their speed is not so important. So I'm afraid the answer is no. – Chayim Friedman Jan 25 '22 at 22:06
@ChayimFriedma if I compile minimal "Hello World" example for GTK4 in C with full debug info and no optimization( `-g3 -O0`) I get only ~600kb exe-file. – ArtDen Jan 26 '22 at 07:38
Why does the debug build size matter for you? – PitaJ Jan 26 '22 at 16:20
@PitaJ I'm worried about my old SSD resource as it lost ~200Mb every time when I build the project – ArtDen Jan 26 '22 at 19:11
@ArtDen Because C is smaller than Rust - that does not means it's optimized there. – Chayim Friedman Jan 26 '22 at 22:17

Reduce application binary size in debug mode

0 Answers0