Setup Environment

The setup command configures environment variables for the MSVC toolchain.

Basic Usage

PowerShell

msvc-kit setup --script --shell powershell | Invoke-Expression

CMD

msvc-kit setup --script --shell cmd > setup.bat && setup.bat

Bash (WSL/Git Bash)

eval "$(msvc-kit setup --script --shell bash)"

Options

Shell Type

--shell <SHELL>  # powershell, cmd, bash

Script Output

--script         # Output as shell script (for eval)

Anchoring the Script Install Root

By default a generated script carries the resolved install directory. --portable-root <PATH> replaces that anchor with PATH, which is used verbatim — a concrete directory or a shell placeholder both work:

# Fixed directory
msvc-kit setup --script --shell cmd --portable-root "D:\build\runtime" > setup.bat

# Relative to the script's own directory (CMD)
msvc-kit setup --script --shell cmd --portable-root "%~dp0runtime" > setup.bat

# Relative to the script's own directory (PowerShell)
msvc-kit setup --script --shell powershell --portable-root "$PSScriptRoot\runtime" > setup.ps1

# Relative to the script's own directory (Bash)
msvc-kit setup --script --shell bash --portable-root "$SCRIPT_DIR/runtime" > setup.sh

The generated script keeps its root indirection (%BUNDLE_ROOT%, $BundleRoot, $BUNDLE_ROOT), so every toolchain path follows the anchor. A Windows anchor given for --shell bash is converted to Unix style (D:\build\runtime becomes /d/build/runtime).

TIP

--portable-root requires --script, and the value must not be empty.

Persistent Setup (Windows Registry)

msvc-kit setup --persistent

WARNING

--persistent requires Administrator privileges and modifies the Windows registry.

Print Environment Variables

Use the env subcommand to print environment variables without applying them:

# As shell script
msvc-kit env

# As JSON (for parsing)
msvc-kit env --format json

JSON Output Example

{
  "VCINSTALLDIR": "C:\\msvc-kit\\VC",
  "VCToolsInstallDir": "C:\\msvc-kit\\VC\\Tools\\MSVC\\14.44.34823",
  "VCToolsVersion": "14.44.34823",
  "WindowsSdkDir": "C:\\msvc-kit\\Windows Kits\\10",
  "WindowsSDKVersion": "10.0.26100.0\\",
  "INCLUDE": "C:\\msvc-kit\\VC\\Tools\\MSVC\\14.44.34823\\include;...",
  "LIB": "C:\\msvc-kit\\VC\\Tools\\MSVC\\14.44.34823\\lib\\x64;...",
  "PATH": "C:\\msvc-kit\\VC\\Tools\\MSVC\\14.44.34823\\bin\\Hostx64\\x64;..."
}

Integration with Build Tools

cc-rs (Rust)

After msvc-kit setup, the cc crate automatically finds the MSVC toolchain:

// build.rs
fn main() {
    cc::Build::new()
        .file("src/native.c")
        .compile("native");
}

CMake

msvc-kit setup --script --shell powershell | Invoke-Expression
cmake -B build -G "NMake Makefiles"
cmake --build build

MSBuild

msvc-kit setup --script --shell powershell | Invoke-Expression
msbuild MyProject.vcxproj /p:Configuration=Release

Profile Integration

PowerShell Profile

Add to $PROFILE:

# Auto-setup MSVC environment
if (Get-Command msvc-kit -ErrorAction SilentlyContinue) {
    msvc-kit setup --script --shell powershell | Invoke-Expression
}

Bash Profile

Add to ~/.bashrc:

# Auto-setup MSVC environment
if command -v msvc-kit &> /dev/null; then
    eval "$(msvc-kit setup --script --shell bash)"
fi