This is the mail archive of the
gsl-discuss@sourceware.cygnus.com
mailing list for the GSL project.
Re: static size
- To: "Diego Saravia" <dsa at unsa dot edu dot ar>
- Subject: Re: static size
- From: Brian Gough <bjg at network-theory dot co dot uk>
- Date: Mon, 26 Jun 2000 21:38:21 +0100 (BST)
- Cc: gsl-discuss at sourceware dot cygnus dot com
- References: <200006232158.SAA23151@inenco.unsa.edu.ar>
- Reply-To: gsl-discuss at sourceware dot cygnus dot com
The final size of executable files should be about the same, since the
linker should only include the .o files that are used by the program.
You can use 'nm' on the executable to see what symbols are being
included. If the whole library is included then that would indicate a
problem that would be worth knowing about.
Diego Saravia writes:
>
>
> I finally be able to do static using autoconf and automake
> Thanks to all people that help me.
>
> I like to compile static because you do not have to distribute or
> compile
> libraries in other machines
>
> When I use static in 0.6 the executable is huge,
> in 0.5 it was smaller
> When gcc links a library, puts all the library code in the executable?
> Is there a way to change that, no using dinamic, so gcc puts only the
> code
> that is used?
>
> Is really easy to work with only one gsl library file, but ...
>
> I have little experience with gcc, sorry if I am doing some silly
> error.
> --
> Diego Saravia
> dsa@unsa.edu.ar
>