Repository navigation
Version 2.0.4
[Summary]
BuildMaster is a small CMake DSL for a graph of other people’s builds.
You declare each dependency once — how it is produced, what it waits on — and the parent gets one shared prefix instead of a pile of ExternalProject / FetchContent glue.
CMake and Meson trees are first-class.
Typical use: add the submodule, add_subdirectory, declare components, then depend / link.
Declaration order does not matter.
The public surface is ten commands on purpose; everything else is internal.
If you landed here from a release link and have not read the tree:
- How to write a component, every optstr key, and the contract: README.md
- The ten names, and nothing else: public_functions.md
- Porting an older caller: MIGRATE.md
Fixed
- GIT accepts patch batches expanded from CMake lists.
GIT={PATCH={${PATCHES}}}applies every list item in order, while following GIT sub-options remain separate. - Reused component skips identify their writer. When a nested configure reuses an existing links file, the status names the component that published it instead of repeating the skipped component's own title. Older links files without a recognizable writer use neutral reuse wording.
- Component
REPACKis idempotent across builds. The publisher archive is snapshotted after installation and never re-used as a merge input; component merges run from the install wrapper before its install stamp closes. Inputs, archiver/recipe and output bytes are stamped, so no-op builds skip the merge while changed members, missing outputs, and interrupted partial archives trigger a safe same-directory rebuild and atomicfile(RENAME)publication.