This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.a_glossary:s:static_library [2021/06/15 14:39] char |
dido:public:ra:xapend:xapend.a_glossary:s:static_library [2021/10/04 02:08] (current) 223.27.121.4 ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== Static Library ===== | ===== Static Library ===== | ||
| - | [[dido:public:ra:xapend:xapend.a_glossary| Return to Glossary ]] | + | [[dido:public:ra:xapend:xapend.a_glossary:start| Return to Glossary ]] |
| - | A **Static Library** or **Statically-Linked Library** is a set of routines, external functions and variables which are resolved in a caller at compile-time and copied into a target application by a compiler, linker, or binder, producing an object file and a stand-alone executable. This executable and the process of compiling it are both known as a static build of the program. Historically, libraries could only be static. | + | A **Static Library** or **Statically-Linked Library** is a set of routines, external functions and variables which are resolved in a caller at compile-time and copied into a target [[dido:public:ra:xapend:xapend.a_glossary:a:application|application]] by a [[dido:public:ra:xapend:xapend.a_glossary:c:compiler|compiler]], linker, or binder, producing an [[dido:public:ra:xapend:xapend.a_glossary:o:object|object]] file and a stand-alone executable. This executable and the process of compiling it are both known as a static build of the program. Historically, libraries could only be static. |
| - | They are usually faster than the shared libraries because a set of commonly used object files is put into a single library executable file. One can build multiple executables without the need to recompile the file. Because it is a single file to be built, use of link commands are simpler than shared library link commands, because you specify the name of the static library. | + | They are usually faster than the shared libraries because a set of commonly used object files is put into a single library [[dido:public:ra:xapend:xapend.a_glossary:e:exec|executable file]]. One can build multiple executables without the need to recompile the file. Because it is a single file to be built, use of link commands are simpler than shared library link commands, because you specify the name of the static library. |
| See: [[dido:public:ra:xapend:xapend.a_glossary:s:shared_libraries]] | See: [[dido:public:ra:xapend:xapend.a_glossary:s:shared_libraries]] | ||