nessi/NexaVPN
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

refactor: migrate Windows target from x86 to x64 architecture

Browse Source 
Update all Windows build configurations, scripts, and documentation from i686-pc-windows-msvc (x86) to x86_64-pc-windows-msvc (x64). Update npm scripts, build-tunnel-helper.sh target validation, bundled helper paths, and tunnel manager strategy references. Add XWIN_ARCH=x86_64 environment variable to Linux cross-build command and --xwin-arch flag to cargo xwin invocation.
This commit is contained in:
Sascha Nesterovic
2026-03-17 19:13:56 +01:00
parent 8d8a3a7859
commit 991df88d58
6 changed files with 24 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/client-platforms.md
View File

@@ -1,19 +1,19 @@
# Desktop Platform Strategy
## Windows x86
## Windows x64
Current MVP integration path:
- NexaVPN enrolls the device and stores the generated profile locally.
- NexaVPN is intended to ship its own bundled Windows x86 tunnel helper.
- NexaVPN is intended to ship its own bundled Windows x64 tunnel helper.
- The end user should interact only with NexaVPN.
- The bundled helper encapsulates the WireGuard runtime internally.
Repository status:
- the NexaVPN tunnel helper CLI is now included in `desktop-client/tunnel-helper/`
- the Windows x86 build can be bundled into `src-tauri/bundled/windows-x86/`
- Ubuntu server builds can cross-compile the Windows x86 helper and Tauri app with `cargo-xwin`
- the Windows x64 build can be bundled into `src-tauri/bundled/windows-x64/`
- Ubuntu server builds can cross-compile the Windows x64 helper and Tauri app with `cargo-xwin`
- the Linux-based Windows packaging path targets NSIS `Setup.exe`; MSI packaging still requires a Windows environment
## macOS ARM