scrap-toolchain

Toolchain registry for scrap — a C/C++ build system.

This repository defines molds (toolchain recipes) and the CI/CD pipeline that validates and distributes them as ingots (prebuilt toolchain packages).

Directory Structure

scrap-toolchain/
├── molds/                          # Toolchain recipes
│   └── {family}/{version}/
│       ├── mold.toml               # Recipe definition
│       └── patches/                # Optional patches (build type only)
├── schema/
│   └── mold-v1.schema.json         # JSON Schema for mold.toml validation
├── scripts/                        # CI/CD helper scripts
├── .github/workflows/              # GitHub Actions workflows
├── platforms.toml                   # Platform matrix (Tier 1/2)
├── index.toml                      # Auto-generated toolchain index
└── README.md

Pipeline Overview

1. A contributor submits a PR adding or updating a molds/{family}/{version}/mold.toml
2. PR Validation — the mold is validated against schema/mold-v1.schema.json, and fetch-type molds are verified on Tier 1 platforms where binaries are defined (Linux platforms are mandatory; macOS is verified when a binary is available)
3. On merge, Ingot Cast — CI processes the mold:
   • fetch molds: no artifacts produced (validation already done in step 2)
   • build molds: CI builds the toolchain and uploads ingots to the distribution platform (not yet implemented)
4. Index Update — index.toml is regenerated from mold definitions and build artifacts, then committed to the repository

Mold Types

• fetch — References prebuilt binaries from upstream (e.g., LLVM official releases). CI validates the recipe but does not produce artifacts; users download directly from upstream.
• build — Builds from source (e.g., GCC). CI produces ingots and uploads them to the distribution platform.

Platform Tiers

Tier	Platforms	Support
Tier 1	linux-x86_64, linux-aarch64, darwin-aarch64	Full CI validation, official distribution
Tier 2	darwin-x86_64	Source build only

License

This repository is licensed under MIT.

Important: The distributed toolchain ingots are subject to their respective upstream licenses, not MIT. Each ingot includes the relevant license files as specified by the metadata.license_files field in its mold.toml.

Toolchain	License	License Files	Status
LLVM/Clang	Apache-2.0 WITH LLVM-exception	LICENSE.TXT	Available
GCC	GPL-3.0-or-later WITH GCC-exception-3.1	COPYING, COPYING.RUNTIME	Planned

How licensing works

• Repository code (scripts, workflows, schema): MIT
• Mold definitions (mold.toml): MIT (as part of the repository)
• Distributed ingots: Each toolchain's own license. The mold.toml metadata.license field declares the SPDX identifier, and metadata.license_files lists the files that must be present in the upstream distribution. cast-ingot.sh verifies their presence during validation.

For contributors adding new molds: ensure metadata.license and metadata.license_files are accurate for the upstream project. The CI pipeline will fail if specified license files are missing from the upstream distribution.