Re: .so, .a and .o-files

[Axel Siebenwirth <axel@hh59.org>]

Hi Ray!

On Thu, 15 Aug 2002, Ray Olszewski wrote:

> .o is an object file. It represents the intermediate step in the 
> compile-and-link process for a program. .so is a shared object file (i.e., 
> a library); their linking (at runtime) is managed by ld.so .

Ok. So I compile from sources many .o's and link them together into an .so
and I have a shared library.

> Depends on how you link. Modern linking is done dynamically (only one copy 
> of the library is loaded into memory and shared by all apps that use it), 
> using .so libraries. Older linking was done statically (each app loaded its 
> own personal copy of the library into memory), using .a libraries.

I figured out that when a program is statically linked, the libraries are in
the executable itself so no additional libraries are required...?

Regards,
Axel
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs