Static Linking - CI/CD Glossary Definition
Static linking bundles all library code into the executable, producing a self-contained binary with no external dependencies at run time.
Static linking copies the machine code of every library a program uses into the final executable at build time, producing a single self-contained binary with no external library dependencies.
Static linking copies the machine code of every library a program uses into the final executable at build time, producing a single self-contained binary with no external library dependencies.
In CI
Statically linked binaries are ideal for containers and deploy artifacts because they run anywhere without matching shared libraries. In Go this is the default; in C, -static or building against musl produces a static binary.
Related guides
Dynamic Linking - CI/CD Glossary DefinitionDynamic Linking: Dynamic linking resolves library references at load time rather than build time, so the exec…
Linker - CI/CD Glossary DefinitionLinker: A linker combines one or more compiled object files, plus referenced libraries, into a single executa…
Shared Library - CI/CD Glossary DefinitionShared Library: A shared library (.so on Linux, .dll on Windows, .dylib on macOS) is a compiled library loade…