aMule Forum

English => Compilation problems => Topic started by: baron-robert on June 05, 2006, 05:38:06 PM

Title: Binaries size
Post by: baron-robert on June 05, 2006, 05:38:06 PM

I compile today the CVS version, and the binaries (amuled & amule) are near 35MB, is it normal?

for the compilation i use this flags:
./configure --prefix=/usr/local/amule-2.1.2CVS --enable-ccache --enable-amule-daemon --enable-amulecmd --enable-webserver --disable-amule-gui --disable-cas --disable-wxcas --disable-alc --enable-alcc

regards

Title: Re: Binaries size
Post by: Gerd78 on June 05, 2006, 05:47:48 PM

Yes, this is perfectly normal because they are compiled with full debuginfo by default. You can disable that or strip the binaries, but please don't post crash reports then, they are not helpful without debuginfo.

Title: Re: Binaries size
Post by: baron-robert on June 05, 2006, 05:51:52 PM

So, if i want to reduce the binaries size, i have to set the option '--disable-debug'?

Title: Re: Binaries size
Post by: Gerd78 on June 05, 2006, 05:54:42 PM

Yes, either that, or execute "make install-strip" instead of "make install", or both.

Title: Re: Binaries size
Post by: skolnick on June 11, 2006, 09:17:29 PM

I think aditional to --disable-debug, it's also neccessary the --enable-optimize switch. That has reduced the size of my binaries to about 4.5MB

Regards.

Title: Re: Binaries size
Post by: Gerd78 on June 11, 2006, 09:32:14 PM

The impact of --enable-optimize on the code size is very system dependent. On some operating systems and hardware platforms and with some GCC versions the binaries will be smaller, in other configurations they will be larger. --enable-optimize and --disable-debug are not really linked to each other.