How do I install the Rust Cross Compile Windows skill?

Run npx skillmds@latest add loopyluci/rust-cross-compile-windows in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Rust Cross Compile Windows skill do?

Use when cross-compiling Rust for or from Windows. It is listed under Coding & Dev Tools on SkillMD.

Is Rust Cross Compile Windows safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Rust Cross Compile Windows?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Rust Cross Compile Windows free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Rust Cross Compile Windows?

LoopyLuci (@loopyluci) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Rust Cross Compile Windows by loopyluci

Name: Rust Cross Compile Windows
Rating: 4.2 (5 reviews)
Author: LoopyLuci

File contents

Rust Cross-Compile on Windows

Cross-compiling Rust applications for and from Windows.

Rust Targets for Windows

# List installed targets
rustup target list --installed

# Common Windows targets:
# x86_64-pc-windows-msvc    (MSVC CRT, most common)
# x86_64-pc-windows-gnu     (MinGW/GCC, no VC++ redist needed)
# i686-pc-windows-msvc      (32-bit MSVC)
# aarch64-pc-windows-msvc   (ARM64 Windows)
# x86_64-unknown-linux-gnu  (Linux target from Windows)

Add Targets

rustup target add x86_64-pc-windows-msvc
rustup target add x86_64-pc-windows-gnu
rustup target add x86_64-unknown-linux-gnu

Building

# Build for MSVC (default)
cargo build --release

# Build for GNU/MinGW
cargo build --release --target x86_64-pc-windows-gnu

# Build for Linux from Windows
cargo build --release --target x86_64-unknown-linux-gnu

Cross-Compile Config (.cargo/config.toml)

[target.x86_64-pc-windows-msvc]
linker = "link.exe"  # MSVC linker

[target.x86_64-pc-windows-gnu]
linker = "x86_64-w64-mingw32-gcc.exe"

[target.x86_64-unknown-linux-gnu]
linker = "x86_64-linux-gnu-gcc.exe"

Using LLVM/Clang Linker

# .cargo/config.toml
[target.x86_64-pc-windows-msvc]
linker = "lld-link.exe"
rustflags = ["-C", "link-arg=-pdbaltpath:%_PDB%"]

Environment Variables

# MSVC
$env:CC = "cl.exe"
$env:CXX = "cl.exe"

# MinGW
$env:CC = "gcc.exe"
$env:CXX = "g++.exe"

# Clang for Windows
$env:CC = "clang-cl.exe"
$env:CXX = "clang-cl.exe"

Cross-Compile C Dependencies

# For crates with C bindings (openssl, vulkan, etc.)
# Set PKG_CONFIG_ALLOW_CROSS=1
# Set CC_<target> for the C compiler per target

# Example: Linux target from Windows
$env:CC_x86_64_unknown_linux_gnu = "x86_64-linux-gnu-gcc.exe"

Pitfalls

MSVC target requires Visual Studio Build Tools -- run from "x64 Native Tools Command Prompt"
GNU target can conflict with MSVC CRT -- mix only with caution
OpenSSL on Windows needs openssl crate with vendored feature
C dependencies need matching cross-compilation toolchains
cargo build without --target uses host target; with --target uses cross toolchain

---name: rust-cross-compile-windowsdescription: Use when cross-compiling Rust for or from Windows.---# Rust Cross-Compile on WindowsCross-compiling Rust applications for and from Windows.## Rust Targets for Windows```powershell# List installed targetsrustup target list --installed# Common Windows targets:# x86_64-pc-windows-msvc (MSVC CRT, most common)# x86_64-pc-windows-gnu (MinGW/GCC, no VC++ redist needed)# i686-pc-windows-msvc (32-bit MSVC)# aarch64-pc-windows-msvc (ARM64 Windows)# x86_64-unknown-linux-gnu (Linux target from Windows)```## Add Targets```powershellrustup target add x86_64-pc-windows-msvcrustup target add x86_64-pc-windows-gnurustup target add x86_64-unknown-linux-gnu```## Building```powershell# Build for MSVC (default)cargo build --release# Build for GNU/MinGWcargo build --release --target x86_64-pc-windows-gnu# Build for Linux from Windowscargo build --release --target x86_64-unknown-linux-gnu```## Cross-Compile Config (.cargo/config.toml)```toml[target.x86_64-pc-windows-msvc]linker = "link.exe" # MSVC linker[target.x86_64-pc-windows-gnu]linker = "x86_64-w64-mingw32-gcc.exe"[target.x86_64-unknown-linux-gnu]linker = "x86_64-linux-gnu-gcc.exe"```## Using LLVM/Clang Linker```toml# .cargo/config.toml[target.x86_64-pc-windows-msvc]linker = "lld-link.exe"rustflags = ["-C", "link-arg=-pdbaltpath:%_PDB%"]```## Environment Variables```powershell# MSVC$env:CC = "cl.exe"$env:CXX = "cl.exe"# MinGW$env:CC = "gcc.exe"$env:CXX = "g++.exe"# Clang for Windows$env:CC = "clang-cl.exe"$env:CXX = "clang-cl.exe"```## Cross-Compile C Dependencies```powershell# For crates with C bindings (openssl, vulkan, etc.)# Set PKG_CONFIG_ALLOW_CROSS=1# Set CC_<target> for the C compiler per target# Example: Linux target from Windows$env:CC_x86_64_unknown_linux_gnu = "x86_64-linux-gnu-gcc.exe"```## Pitfalls- **MSVC target** requires Visual Studio Build Tools -- run from "x64 Native Tools Command Prompt"- **GNU target** can conflict with MSVC CRT -- mix only with caution- **OpenSSL** on Windows needs `openssl` crate with `vendored` feature- **C dependencies** need matching cross-compilation toolchains- **cargo build** without --target uses host target; with --target uses cross toolchain

Frequently asked questions

Rust Cross Compile Windows