Documentation Index
Fetch the complete documentation index at: https://mintlify.com/SGizek/Raiku/llms.txt
Use this file to discover all available pages before exploring further.
raiku doctor probes your system for every build tool that Raiku packages may invoke during installation. For each tool it reports whether the binary is on PATH, what version is installed, and — when missing — a direct link or command to obtain it. This makes doctor the ideal first diagnostic step when a package install fails with a build error, or when setting up Raiku on a new machine.
Usage
Flags
| Flag | Short | Description |
|---|---|---|
--language | -l | Check tools for a single language only (e.g. Rust, Python, Go). |
Tools checked
| Tool | Command | Language | Required |
|---|---|---|---|
| Python | python | Python | ✅ Yes |
| pip | pip | Python | ✅ Yes |
| GCC | gcc | C/C++ | Optional |
| Clang | clang | C/C++ | Optional |
| CMake | cmake | C++ | Optional |
| Cargo | cargo | Rust | Optional |
| Zig | zig | Zig | Optional |
| Java (javac) | javac | Java | Optional |
| Go | go | Go | Optional |
| dotnet | dotnet | C# | Optional |
| git | git | General | ✅ Yes |
python, pip, git) must be present for Raiku to function at all. Optional tools are only needed when you install packages for the corresponding language.
Doctor also verifies key Raiku home directories:
| Check | Description |
|---|---|
~/.raiku/ exists | Raiku home directory is initialised. |
| Cache directory exists | Package cache is present. |
| Index cached | ~/.raiku/index.json has been synced at least once. |
Examples
Sample output
Run
raiku doctor immediately after installing Raiku on a new machine to confirm your toolchain is ready before attempting your first package install. If required tools are missing, Raiku will report them in red and exit with a non-zero code.