1.2 KiB
1.2 KiB
BTC (Build Tool Chain) Quickstart: 0.3.1
This guide outlines the integration of the BTC 0.3.1 Sovereign Forge into your swarm environment.
1. Prerequisites
- Environment: A standard Linux host (Debian/Arch/Fedora) capable of running native
gcc. - Permissions: Root (EUID 0) is required for
ramfsmounting and hardware-level forensic stamping. - Storage: Ensure
/opt/BTCis available as a persistent storage container for logs, release archives, and cached source tarballs.
2. The Forge Pipeline
The forge executes in four distinct phases:
- Probe: Silicon topology is scanned, and thread counts are optimized for the available RAM (preventing LTO thrashing).
- Setup: A volatile cleanroom (
ramfs) is provisioned. - Forge: Core components (Binutils, Kernel Headers, GCC Pass 1, Glibc, Libxcrypt, GCC Pass 2, Kernel) are built sequentially.
- Package: The resulting toolchain is compressed into a "Golden Image" tarball for deployment.
Basic Execution
# Standard Build (Baseline Profile)
sudo ./BTC-0.3.1.sh base
# Hardened Build (Ghost Profile - No modules, restricted debugging)
sudo ./BTC-0.3.1.sh ghost
# Deployment Build (Targeting a specific disk device)
sudo ./BTC-0.3.1.sh ghost /dev/sda3