|compiler, linker and libraries firstname.lastname@example.org (TC Shen) (2001-06-21)|
|Re: compiler, linker and libraries email@example.com (Lionel Brits) (2001-06-28)|
|Re: compiler, linker and libraries firstname.lastname@example.org (Matthew J. Lockner) (2001-07-01)|
|Re: compiler, linker and libraries email@example.com (2001-07-03)|
|From:||"Lionel Brits" <firstname.lastname@example.org>|
|Date:||28 Jun 2001 23:46:34 -0400|
|Posted-Date:||28 Jun 2001 23:46:34 EDT|
Experience with software development tools will probably give you a better
understanding, but here goes (no link)
A compiler takes source code and translates it into an object file
comprising machine instructions.
A linker takes one or more object files and relocates code into a machine
exacutable file that is ready to be executed.
A library is just a collection of object files stored in a single file that
can be used by more than one program (the idea of reusable code).
Libraries can be statically linked by the linker, so that only the parts
that are needed are included in the executable file, or they can be
dynamically linked when the executable is run, such as .DLL files in the
- Lionel Brits
"TC Shen" <email@example.com> wrote in message
> Can anyone show me links to explanation of the relations among
> compilers, linkers and libraries. How they work with each other?
Return to the
Search the comp.compilers archives again.