Definition
A build system is the software responsible for turning source code into a working artifact — an executable, a library, a container image, a deployable bundle — by automating the dependency-aware sequence of compilation, linking, code generation, asset processing, and packaging steps. At its core a build system is a dependency graph executor: each target declares what it needs, the system figures out the correct order, and only the parts whose inputs have changed get rebuilt.
The family ranges from the venerable make, which uses timestamps on a declarative Makefile, to modern hermetic systems like Bazel and Buck that build the entire dependency graph from explicit declarations and aggressively cache intermediate results. Higher-level wrappers — cmake, autotools, Meson — generate the lower-level rules for a specific platform. Language-specific tools like Gradle, Maven, Cargo, and npm play the same role with idioms tuned to their ecosystem.
Why it matters
How it works
Every build system shares the same core algorithm. First, a description file enumerates targets and the inputs each target depends on — source files, generated files, output of other targets. Second, the system walks the dependency graph and computes the minimum set of work needed to bring every requested target up to date, given the inputs that have changed since the last build. Third, it executes that work, ideally in parallel where the graph allows. Intermediate results are typically cached, and modern systems hash inputs rather than just checking timestamps so caches survive across machines.
The major differences across systems are about granularity and trust. Make trusts the user to declare dependencies correctly and trusts the file system clock; Bazel demands that dependencies be declared exhaustively and verifies them by sandboxing each action. Package-manager-style systems (Cargo, npm) integrate dependency resolution from the network into the same graph. The trade-off is always between flexibility — letting the build escape its sandbox to do unusual things — and reproducibility, which requires the sandbox stay closed.