ddidderr/softlan-vpn
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: clarify Windows build shell preflight

Browse Source 
The MVP test guide already asks the tester to verify that the MSVC tools are
available, but the full Windows client build depends on native C tooling through
its dependency stack. Make the expected shell explicit so a missing `cl`, `lib`,
or `link` failure points directly to Visual Studio Build Tools setup instead of
looking like a Rust or project error.

Test Plan:
- git diff --check

Refs: MVP Windows client build handoff
This commit is contained in:
ddidderr
2026-05-22 09:11:44 +02:00
parent 8f09fea6f3
commit 9abdd2cb1c
1 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
TESTING.md
+5
View File
@@ -87,6 +87,11 @@ with the C++ build tools. The dependency stack includes native code, so tools
such as `cl.exe` and `lib.exe` must be available in the build environment. such as `cl.exe` and `lib.exe` must be available in the build environment.
TAP-Windows6 must be installed before running the client. TAP-Windows6 must be installed before running the client.
Use an elevated **x64 Native Tools Command Prompt for VS** or **Developer
PowerShell for VS** for the Windows build and client run. If the commands below
cannot find `cl`, `lib`, or `link`, install or repair Visual Studio Build Tools
with the C++ build tools and Windows SDK, then reopen the developer shell.
Quick Windows checks: Quick Windows checks:
```powershell ```powershell