# Install, update and develop Every way to install rust-anything, keep it up to date, remove it, and build it from source. Back to the [README](../README.md). ## Install ```sh cargo install --path . ``` `record`, `diff` and `bench` run the original in its own runtime: Node 22.6+ for TS (it runs `.ts` sources directly), Python 3.9+ for Python and C (ctypes), Go 1.21+, Ruby 3+, JDK 17+ (`javac` and `java`). `profile` on Node needs Node 24+, which allows `--cpu-prof` in `NODE_OPTIONS`. C also needs a C compiler. wasm bridges also need `rustup target add wasm32-unknown-unknown` and `cargo install wasm-bindgen-cli --version --locked`; `build` names the exact version. ### Windows Native Windows CI uses the `x86_64-pc-windows-msvc` Rust target. Install the stable MSVC toolchain and Visual Studio Build Tools with the **Desktop development with C++** workload; the C compiler and linker are required for C bridges and native Rust extensions. Install the runtime for the source language you are migrating. Python may be available as either `python3` or `python`; rust-anything detects both. The GNU Windows target is not exercised by CI. Run the native bridge integration suite from a Developer PowerShell prompt: ```powershell rustup default stable-x86_64-pc-windows-msvc cargo test --locked --test native -- --nocapture ``` The suite builds and loads real DLL-backed Node and Python extensions and the supported native bridges for each runtime present on `PATH`. Missing optional runtimes are reported as skipped; Cargo, the active Rust standard library, and the MSVC linker are required. If Cargo reports that it cannot find `std`, reinstall the active target with `rustup target remove x86_64-pc-windows-msvc` followed by `rustup target add x86_64-pc-windows-msvc`. If linking fails, run from a Visual Studio Developer PowerShell and verify that `where.exe link` finds the MSVC linker. Tests use temporary folders, including a path with spaces and Unicode characters, and remove generated artifacts after a successful run. For agents, `rust-anything setup` registers everything (see Quick start). To add the MCP server to one project by hand instead (`.mcp.json`): ```json { "mcpServers": { "rust-anything": { "command": "rust-anything", "args": ["mcp"] } } } ``` Every tool, its parameters and what it may touch: [docs/tools.md](tools.md). The server also offers two prompts, `port_unit` and `port_whole_app`, built from the skill. ## Development ```sh cargo test # unit tests, fixture repo, record/diff/shadow loop (needs node), app record/replay per language cargo clippy --all-targets -- -D warnings cargo fmt ``` Design choices and their reasons: [DECISIONS.md](../DECISIONS.md). ## Update or remove ```sh cargo install rust-anything # update (Cargo) npm install -g rust-anything@latest # update (npm) rust-anything setup # refresh agent settings rust-anything setup --remove && cargo uninstall rust-anything # remove (Cargo) rust-anything setup --remove && npm uninstall -g rust-anything # remove (npm) ``` `setup --remove` takes out only rust-anything's entries; the copies it saved (`.rust-anything.bak`) stay until you delete them.