Installing & Compiling Rogue
Rogue supports several installation and build workflows, depending on whether you want a prebuilt package, a source build, or a containerized runtime.
Most users should start with a Miniforge-based workflow. It gives Rogue a managed Python environment, keeps dependencies predictable, and matches how the project is commonly developed and tested.
In practice there are three main paths:
Install a prebuilt Rogue package into Miniforge: Installing Rogue With Miniforge
Build Rogue from source inside Miniforge: Building Rogue Inside Miniforge
Build Rogue from source outside Miniforge: Building Rogue From Source
Recommended Choices By Platform Are:
Linux: Installing Rogue With Miniforge or Building Rogue Inside Miniforge
macOS arm64: Building Rogue Inside Miniforge
Windows: Setting Up Ubuntu On Windows, then use Installing Rogue With Miniforge inside WSL2 or use Running Rogue With Docker
Native source builds outside Miniforge are mainly for environments that already have their own dependency and deployment model. For most application users, Miniforge is the simpler path.
What This Section Covers
Miniforge install and source-build workflows
Native source builds
Docker-based usage
Platform-specific notes such as WSL2 and firewall constraints
Packaging-oriented notes such as Yocto integration and external application builds