dynamically loaded libraries (size of)

[Kartik Jayaraman]

Hi Christian,

	If you link with a shared library (.so), the size would be smaller than the
size if linked with a static library( .a ).

Ideally for a shared libraries only descriptors for the functions used are
mentioned in the executable. So no matter how big the .so is the executable
size would not hold descriptors for all the functions present in the .so.


-Kartik

 -----Original Message-----
From: 	gcc-help-owner@gcc.gnu.org [mailto:gcc-help-owner@gcc.gnu.org]  On
Behalf Of Christian Schäfer
Sent:	Wednesday, December 18, 2002 12:27 PM
To:	gcc-help@gcc.gnu.org
Subject:	dynamically loaded libraries (size of)

hi all,

I am currently developing a library for some opengl stuff and I want
to compile it later to a linkable library. that would not be a problem
and even if it was I would find enough tutorials over the net.

but what is unclear to me is the following:
when I compile a (quiet big) library and link it in another project,
which makes only little use of the library, to what matter will the
library increase the size of the project?
will only the used functionality be a part of the new compiled
executable or will the whole library be included and will the project
therefor be of much much bigger size than it had to be?


regards
/Christian                   mailto:caefer@krachstoff.net

---


I propose that the following character sequence for joke markers:

:-)

                             19-Sep-82 11:44    Scott E  Fahlman