RadBuild 0.2.1

RadBuild 0.2.1 is the Crimson experimental build framework for Radical Computer Technologies projects. It uses schema v2 JSON project files to build FPGA designs, Linux/embedded software graphs, RADPx OS images, package metadata, and deployment artifacts through one CLI.

Release Channels

• Suite: experimental
• Schema: 2.0
• Package format: frozen release executables for RadBuild runtime packages
• Primary CLI: radbuild
• IDE integration: line-delimited JSON events for VSCode and other frontends

Documentation Sections

• Install
• FPGA Builds
• OS Builds
• Packaging
• Examples
• Settings Fields
• Reference
• Compatibility Appendix

Quick Start

sudo apt install ./radbuild_0.2.1_amd64.deb
radbuild project create --list-templates
radbuild project create ./workspace --non-interactive --template fpga-mpsoc-buildroot --project-name demo
radbuild project register ./workspace/demo
radbuild project list --json
radbuild project validate --settings ./workspace/demo/settings.json
radbuild generate --settings ./workspace/demo/settings.json
radbuild build all --settings ./workspace/demo/settings.json --dry-run --json-events

Expected dry-run output begins with JSON events:

{"event":"build_started","systems":2}
{"event":"system_planned","system":"vivado","type":"fpga.vivado"}
{"event":"system_planned","system":"petalinux","type":"linux.petalinux"}
{"event":"build_finished","status":"dry-run"}

VSCode Front-End

The radbuild-vscode-support package includes a VSCode extension with a RadBuild activity-bar view. The first view lists registered projects with a single Open action. Opening a project switches VSCode to that source root and changes the side panel into a project detail view with baseline settings, artifact status, build actions, RADPx OS configuration, and a form-based project settings editor. The Projects pane keeps project rows simple while exposing Toolchain Setup, Register Directory, and Create Project in the pane toolbar. A directory is accepted as a RadBuild project only when it contains a schema v2 settings.json.

The create-project UI is template-aware: changing templates resets fields to that template's defaults and disables fields that do not apply. Toolchain setup rescans on extension activation and when opened. Vivado roots are normalized to the folder containing version subdirectories such as 2024.1, and versions are accepted only when they contain settings64.sh plus bin/vivado. PetaLinux roots are handled the same way, using settings.sh plus a valid petalinux-build path.