Expand description
doctor: checks the toolchain a game on the engine builds with: Rust
and Cargo, rustup’s targets, MSYS2’s linker and objcopy on the
Windows GNU toolchain (AGENTS.md), on Linux the C linker, pkg-config and the
system libraries the backend links and opens, and the web target.
Each check says what it found and, if it failed, how to fix it (its
help): on Linux, the install command for the distribution’s package
manager (/etc/os-release), and scripts/setup-linux.sh, which
installs the same list. It passes when
every check does; when one fails, it answers codes::TOOLCHAIN and
exits 3.
What it runs and looks at goes through a Probe, so its tests can
give it any machine.
Structs§
- Check
- One check.
- Doctor
Input - What
doctorchecks: everything (nothing to choose yet). - Doctor
Output - What
doctorfound. - This
Machine - The machine
doctorruns on.
Constants§
- MSYS2_
GCC - Where MSYS2 puts the mingw-w64 GCC that links on the Windows GNU
toolchain (the engine’s
.cargo/config.tomlnames it as the linker). - WASM_
TARGET - The web build’s target.
Traits§
- Probe
- How
doctorlooks at the machine.