Ninja is a small build system with a focus on speed. It differs from other build systems in two major respects: it is designed to have its input files generated by a higher-level build system, and it is designed to run builds as fast as possible.

bmake is a program designed to simplify the maintenance of other programs. Its input is a list of specifications as to the files upon which programs and other files depend.

osc is a command line interface to the Open Build Service. It allows you to checkout, commit, perform reviews etc. The vast majority of the OBS functionality is available via commands and the rest can be reached via direct API calls.

autosetup is a tool, similar to autoconf, to configure a build system for the appropriate environment, according to the system capabilities and the user-selected options.

This package provides the ninja command, implemented as a symbolic link to the samu command of samurai package.

Potato Make is a Scheme library that aims to simplify the task of maintaining, updating, and regenerating programs. It is inspired by the POSIX make utility and allows writing a build script in Guile Scheme.

Tup is a generic build system based on a directed acyclic graphs of commands to be executed. Tup instruments your build to detect the exact dependencies of the commands, allowing you to take advantage of ideal parallelism during incremental builds, and detecting any situations where a build worked by accident.

GN is a tool that collects information about a project from .gn files and generates build instructions for the Ninja build system.

samurai is a ninja-compatible build tool written in C99 with a focus on simplicity, speed, and portability. It is feature-complete and supports most of the same options as ninja. This package provides the command samu. For a ninja command replacement, use the samu-as-ninja-wrapper package.

This package contains an implementation of POSIX make. The default configuration enables extensions. Generally these extensions are compatible with GNU make.

Build is a massively-parallel software build system implemented on top of GNU Make, designed with the following tasks in mind:

• configuration

• building

• testing

• installation

Build has features such as:

• Position-independent makefiles.

• Non-recursive multi-makefile include-based structure.

• Leaf makefiles are full-fledged GNU makefiles, not just variable definitions.

• Complete dependency graph.

• Inter-project dependency tracking.

• Extensible language/compiler framework.

xmake is a cross-platform build utility based on Lua. Features:

• Built-in caching and parallel compilation,

• Concise Lua syntax,

• Custom rules, plugins and modules,

• Support for C++20 modules and compile_commands.json,

• Support for languages outside C/C++ (e.g. Go, Rust, Zig).

A JSON compilation database is used in the Clang project to provide information on how a given compilation unit is processed. With this, it is easy to re-run the compilation with alternate programs. Bear is used to generate such a compilation database.

Bam is a fast and flexible build system. Bam uses Lua to describe the build process. It takes its inspiration for the script files from scons. While scons focuses on being 100% correct when building, bam makes a few sacrifices to acquire fast full and incremental build times.

Muon is an implementation of the meson build system in c99 with minimal dependencies.

Maak is a command runner and control plane for your projects. It allows you to use the power of Lisp (Guile Scheme) to define your tasks, build steps, repetitive tasks or other automation.

With Maak you can easily call external shell commands and integrate with your existing scripts and tools. It is inspired by the GNU Make utility but it does away with a lot of the complexity that comes with its history.

Waf is a build system framework for configuring, compiling and installing applications.

Features:

• Automatic build order: the build order is computed from input and output files, among others

• Automatic dependencies: tasks to execute are detected by hashing files and commands

• Performance: tasks are executed in parallel automatically, the startup time is meant to be fast (separation between configuration and build)

• Flexibility: new commands and tasks can be added very easily through subclassing, bottlenecks for specific builds can be eliminated through dynamic method replacement

• Extensibility: though many programming languages and compilers are already supported by default, many others are available as extensions

• IDE support: Eclipse, Visual Studio and Xcode project generators (waflib/extras/)

• Documentation: the application is based on a robust model documented in The Waf Book and in the API docs

• Python compatibility: cPython 2.7 to 3.x, Jython 2.7 and PyPy

ACR tries to replace autoconf functionality generating a full-compatible configure script, but relying on Bourne shell script instead of m4.

premake5 is a command line utility that reads a scripted definition of a software project and outputs Makefiles or other lower-level build files.

haredo is a build automator. It is an alternative to e.g. make(1) and redo(1). Features:

• Script syntax is plain shell script,

• Only one command with few extraneous rules,

• .do files are short and modular like in redo,

• Builds its dependency tree on the fly, uses no database,

• Doesn't break the build state when interrupted.

ToyBox combines tiny versions of many common UNIX utilities into a single small executable. It provides a fairly complete environment for any small or embedded system.

BusyBox combines tiny versions of many common UNIX utilities into a single small executable. It provides a fairly complete environment for any small or embedded system.

QBE is a small compiler backend using an SSA-based intermediate language as input.

simdutf is a C++ library providing Unicode routines (UTF8, UTF16, UTF32). These routines are optimized for many specific architectures using SIMD (Single Instruction, Multiple Data) instructions.