minsize buildtype

[EmixamPP]

• meson version: 1.5.1
• gcc version: 13.3.1

I went through the different build types proposed by meson, and I see that buildtype=minsize sets debug=true and optimization=s. Wouldn't it make sense to set debug=false instead? Because debug=true adds symbols to the target and thus increases its size significantly.

Also, it would make sense to add strip=true when buildtype=minsize is set, to further reduce the size. (Personally, I would also enable it when buildtype=release)

On my project, I report the following sizes for my standalone executable:

• optimization=s + debug=true = buildtype=minsize = 14M
• optimization=s + debug=false = 7.8M
• optimization=s + debug=false + strip=true = 6.1M
• optimization=s + debug=true + strip=true = 6.1M
• optimization=3 + debug=false = buildtype=release = 7.9M
• optimization=3 + debug=false + strip=true = 6.3M
• optimization=0 + debug=true = buildtype=debug = 14M
• optimization=0 + debug=true + strip=true = 6.6M

As you can see, buildtype=minsize seems a bad name, since it is as big as buildtype=debug (without strip=true).

I can PR this change if you're interested.

A last question, I'm wondering why it is optimization=0 that has been chosen for buildtype=debug, and not optimization=g, although I guess debug=true enables that?

[EmixamPP]

In addition, meson setup|configure allows enabling --strip and --debug but there is no possibility to set them false, which limits the combinations of what we can set as default option and what can be modified/added manually.