Continuous integration

Build C-- programs (workflows/build.yaml)

Runs on every push to main and on every pull request. It compiles every C-- program in the repository and fails if any target stops building, so a change that breaks compilation is caught before merge.

Unlike the main kolibrios build, this repository does not build a toolchain: the c-- compiler is committed here (c--/c--.elf, a static 32-bit i386 Linux binary), so the job simply runs it over every program.

The heavy lifting is in build.sh:

• it walks every Tupfile.lua and reads the declared c-- rule, so the set of built programs stays in sync with the real tup build — add a program with a Tupfile.lua and CI picks it up automatically;
• tup.foreach_rule("*.c", …) directories (examples/, misc/) build every source file, single-tup.rule directories build their one target;
• /D=AUTOBUILD and the /D=LANG_* define are applied exactly as the Tupfile.lua requests;
• a target is considered built only if c-- exits 0 and produced a non-empty .com; a crash or hang (the known heap-layout-dependent c-- flakiness) is caught by a per-compile timeout and retried up to 4 times before being reported as a failure.

Language variants LANG_ENG and LANG_RUS build in parallel.

The compiled .com files are collected under dist/ and published as a per-language artifact (cmm-programs-LANG_ENG / cmm-programs-LANG_RUS), downloadable from the run's Summary page for 14 days.

Running it locally

# Linux (uses the in-repo c--.elf):
./build.sh LANG_ENG

# Windows / Git Bash (point CMM at the .exe):
CMM=./c--/c--.exe sh build.sh LANG_ENG

Runner

The job uses the kolibri-toolchain runner, the same self-hosted runner label as the main kolibrios build. If that label is not available to this repository, change runs-on: in workflows/build.yaml to a runner that can execute a 32-bit static ELF (any x86-64 Linux with IA32 emulation).