vcv-rs 0.1.0

Fast Visual Studio environment setup
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117

# vcv

Fast Visual Studio environment setup. **~50x faster** than `vcvars64.bat`.

| | Time |
|---|---:|
| `vcv` | ~20ms |
| `vcvars64.bat` | ~2000ms |

## Why?

Microsoft's `vcvars64.bat` is slow because it:
- Spawns PowerShell for telemetry
- Runs 15+ batch files sequentially
- Queries registry multiple times
- Searches directories with `dir` commands

This tool does the same job with:
- Single `vswhere.exe` call (~20ms)
- Direct registry lookups
- Zero telemetry
- Native compiled binary

## Installation

```powershell
# Build from source
cargo build --release
copy target\release\vcv.exe C:\bin\
```

## Usage

### PowerShell

```powershell
# Apply environment (auto-detect shell)
vcv | iex

# Quiet mode
vcv -q | iex

# Add to $PROFILE
function vcvars { vcv @args | iex }
```

### CMD

```cmd
vcv -f cmd > vcenv.bat && vcenv.bat

:: Or inline
for /f "delims=" %i in ('vcv -f cmd') do @%i
```

### Bash / MSYS2

```bash
eval $(vcv -f sh)
```

### JSON (for tools)

```powershell
vcv -f json -q
```

## Options

```
-a, --arch      Target architecture: x64 (default), x86, arm64
-s, --host      Host architecture: x64 (default), x86, arm64
-f, --format    Output format: auto (default), ps, cmd, sh, json
-v, --vs        VS version year: 2017, 2019, 2022
-q, --quiet     Suppress info messages
--no-validate   Skip cl.exe validation
-h, --help      Print help
```

## Examples

```powershell
# x64 native (default)
vcv | iex

# x86 target
vcv -a x86 | iex

# Cross-compile for ARM64
vcv -a arm64 | iex

# Use specific VS version
vcv -v 2019 | iex

# JSON for parsing
vcv -f json | ConvertFrom-Json
```

## Output

**Note:** All paths are prepended (added to the beginning), not replaced. Your existing PATH, INCLUDE, etc. remain intact - VS tools just get priority.

Sets these environment variables:

| Variable | Description |
|----------|-------------|
| `PATH` | Compiler binaries, SDK tools |
| `INCLUDE` | Headers (VC++, SDK, UCRT) |
| `LIB` | Libraries for linking |
| `LIBPATH` | Assembly references |
| `VCToolsInstallDir` | VC++ toolset path |
| `WindowsSdkDir` | Windows SDK path |
| `UCRTVersion` | Universal CRT version |

## License

MIT