Development environment

Toolchain scope

The workspace uses edition 2024 and declares no MSRV. Local runs used Rust 1.96.0 on Windows with both the GNU and MSVC toolchains. Linux and macOS compile but have not run the tests on a real machine.

The commands below reproduce the repository’s documented development setup. They are not a uuldana-cli installer. Run them only in a source checkout you control.

Windows GNU

The PowerShell setup installs a specific Rust toolchain and runs the repository’s pinned binutils installer:

powershell

rustup toolchain install 1.96.0-x86_64-pc-windows-gnu --profile minimal --component rustfmt --component clippy
rustup override set 1.96.0-x86_64-pc-windows-gnu
./scripts/install-windows-gnu.ps1

For each new shell, activate the native tools and inspect their versions:

powershell

. ./scripts/enter-windows-gnu.ps1
rustc -vV
as --version
dlltool --version

The installer verifies pinned MSYS2 archive hashes and installs under a per-user local toolchain directory. Complete native MinGW binutils are required; mixing MSYS tools with native MinGW tools is not a supported workaround.

Windows MSVC

Use the MSVC Rust toolchain with the Visual Studio Build Tools “Desktop development with C++” workload and a Windows SDK. A linker executable alone is not enough. Run verification from a matching x64 developer shell.

Test helper

Some process tests use a small helper built outside the workspace, because the workspace forbids unsafe_code. scripts/prepare-test-helper.ps1 builds it, and scripts/verify-windows.ps1 calls it for you.

Verification output

The verification scripts write logs and artifacts under target/verification in your checkout.

Navigation