27 lines
1.2 KiB
Markdown
27 lines
1.2 KiB
Markdown
# 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 `ramfs` mounting and hardware-level forensic stamping.
|
|
* **Storage:** Ensure `/opt/BTC` is 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:
|
|
|
|
1. **Probe:** Silicon topology is scanned, and thread counts are optimized for the available RAM (preventing LTO thrashing).
|
|
2. **Setup:** A volatile cleanroom (`ramfs`) is provisioned.
|
|
3. **Forge:** Core components (Binutils, Kernel Headers, GCC Pass 1, Glibc, Libxcrypt, GCC Pass 2, Kernel) are built sequentially.
|
|
4. **Package:** The resulting toolchain is compressed into a "Golden Image" tarball for deployment.
|
|
|
|
### Basic Execution
|
|
```bash
|
|
# 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 |