Meaning
Build process stage that combines multiple compiled code modules into a single executable binary or library. The operation of object file linking resolves symbolic references across different modules to create a unified address space. This step is necessary to produce an operational firmware image or application from structured source files.
It is limited to resolving references that are defined within the input object files or referenced external libraries.
Symbol Resolution
Compiler outputs must be integrated into a continuous layout. During object file linking, the linker matches function calls with their actual entry points in other modules. This action ensures that the execution flow moves correctly across module boundaries.
Memory Allocation
Target platform memory layouts are defined by a linker script. This file guides object file linking in placing sections of code and variables into specific physical memory regions. For embedded devices, this process ensures that critical routines are stored in fast execution memory.
Integration Test
Continuous integration pipelines execute the build script to generate the final binary. A successful object file linking phase is followed by automated unit and integration tests to verify the behavior of the built image. Maintaining a clean link phase reduces memory footprint and eliminates dead code, resulting in more efficient executable binaries for the target microcontrollers.