Platforms
Bricks-OS contains ports for several consoles and for i386 PCs. The table below describes the source tree and historical build interface. It does not claim that the targets currently build with modern toolchains.
| Target | Architecture | Top-level makefile | Historical toolchain notes |
|---|---|---|---|
pc |
i386 | Makefile.pc |
Linux GCC, freestanding 32-bit build |
gba |
ARM | Makefile.gba |
devkitPro, arm-eabi-* tools |
nds |
ARM7 and ARM9 | Makefile.nds |
devkitPro, arm-eabi-* tools |
ngc |
PowerPC | Makefile.ngc |
devkitPro, powerpc-gekko-* tools |
wii |
PowerPC | Makefile.wii |
devkitPro, powerpc-gekko-* tools |
ps1 |
MIPS | Makefile.ps1 |
Cross-toolchain support present in tree |
ps2 |
MIPS EE and IOP | Makefile.ps2, Makefile.ps2-ee, Makefile.ps2-iop |
ps2dev |
psp |
MIPS | Makefile.psp |
devkitPro-era PSP toolchain |
dc |
SuperH | Makefile.dc |
sh-elf-* tools |
Feature Selection
Target-specific configuration lives under:
kernel/include/include-<arch>/include-<target>/asm/arch/config.make
kernel/include/include-<arch>/include-<target>/asm/arch/config.h
The makefile configuration selects source modules. The matching C/C++ header selects compile-time behavior. When restoring a target, keep these two files in sync.
Docker Restoration
The proposed cross-platform workflow uses separate pinned Linux toolchain images for target families instead of installing SDKs directly on each host. See the Modernization Plan for the image matrix and restoration milestones.
Verification Policy
For each restored target, record:
- Exact SDK or container version.
- Build command.
- Produced binary path.
- Emulator or hardware launch procedure.
- Observable smoke-test output.