I did not want to submit it as a bug, but I think next lines should not be
if test "x$GCC" = "xyes"; then
CFLAGS="$CFLAGS -Wall -g3"
so I have /usr/local/gaim 18Mb instead of 970kb
or am I missing something?
From: Mark Doliner <mark@ki...> - 2004-11-04 02:42:05
On Thu, 2 Sep 2004 12:59:15 +0300 (EEST), Oleg Batrashev wrote
> I did not want to submit it as a bug, but I think next lines should
> not be in configure.ac
> if test "x$GCC" = "xyes"; then
> CFLAGS="$CFLAGS -Wall -g3"
> fi AC_SUBST(CFLAGS)
> so I have /usr/local/gaim 18Mb instead of 970kb
> or am I missing something?
This email is 2 months old, but I don't believe anyone ever responded.
-Wall means "show more warnings when compiling." This flag should have no
effect on the size of the compiled Gaim.
-g3 means "compile with extended debugging info. Removing this flag only
reduced the size of my Gaim install by 4MB
I have a feeling you're really asking about stripping. Running "strip" on the
the gaim binary and all the .so's in the lib directory brings my install down
from 66MB to 12MB (scandalous!).
So your question should really be, "Shouldn't Gaim strip it's binary files
when installing them?" Personally I'd say the answer is no. I feel that
distributions should determine whether they want to strip the binary or not (I
believe Red Hat, Debian and Gentoo all strip their binaries (Gentoo has an
option in the config file for emerge or something, right?)). If someone
compiles Gaim themselves, it seems like a good idea to keep the debugging
info. In my mind the only reason someone would want to compile Gaim
themselves is to do development on it, or on a plugin. In which case
debugging info is useful.
I'm probably not the best person to comment on this kind of thing though. I
just wanted to give SOME answer.
O O Mark Doliner
\ | mark@...
\ | http://www.kingant.net
"There needs to be a better word for weird."