what is the difference between compiler and linker in c?
+5
A:
The compiler converts code written in a human-readable programming language into a machine code representation which is understood by your processor. This step creates object files.
Once this step is done by the compiler, another step is needed to create a working executable that can be invoked and run, that is, associate the function calls (for example) that your compiled code needs to invoke in order to work. For example, your code could call sprintf, which is a routine in the C standard library. Your code has nothing that does the actual service provided by sprintf, it just reports that it must be called, but the actual code resides somewhere in the common C library. To perform this (and many others) linkages, the linker must be invoked. After linking, you obtain the actual executable that can run.
Stefano Borini
2010-09-30 14:08:52
+1 good explanation. Note that on most OS, there are actually *two* linkers involved: The linker that runs after compilation and produces the executable file (usually just called "linker"), and the linker that links in dynamically loaded libraries (aka .so or .dll) at execution time (usually called "dynamic linker").
sleske
2010-09-30 14:14:07
+2
A:
A compiler generates object code files (machine language) from source code.
A linker combines these object code files into an executable.
Many IDEs invoke them in succession, so you never actually see the linker at work. Some languages/compilers do not have a distinct linker and linking is done by the compiler as part of its work.
Oded
2010-09-30 14:10:02