windows: bundle cuFFT in installer and tag the CUDA/CPU variant

cuFFT is the only CUDA component linked dynamically (cudart and the fast-feedback indexer are static), so the prior Windows installer would fail to launch the GPU path on a host without a CUDA toolkit. Ship cufft64_*.dll next to the viewer (CUDA 13 keeps it in bin/x64, earlier toolkits in bin); the DLL is self-contained, so the installed app needs only an NVIDIA driver. Tag the variant where it matters and nowhere else: the installer filename (-cuda<major> / -cpu) and the Add/Remove Programs entry ("Jungfraujoch (CUDA)" / "(CPU)") advertise it, while the install folder and Start Menu group stay plain "Jungfraujoch" -- the CUDA build is a strict superset, so the two variants share a location and replace each other. Docs: SOFTWARE.md + JFJOCH_VIEWER.md. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-21 09:17:52 +02:00
parent 0c1babd0ca
commit ec8a45dc09
4 changed files with 51 additions and 8 deletions
@@ -10,7 +10,9 @@ but likely possible with providing some packages from external repositories.
 The desktop viewer `jfjoch_viewer` (only) can additionally be built on **Windows 11** with Visual
 Studio 2026 (MSVC), CUDA 13.3 and Qt 6.11 — see
 [jfjoch_viewer ▸ Building from source on Windows](JFJOCH_VIEWER.md#building-from-source-on-windows).
-The rest of Jungfraujoch is Linux-only.
+The Windows installer bundles the Qt runtime, and on the CUDA build the CUDA runtime (cuFFT) as
+well, so end users need neither Qt nor a CUDA toolkit installed — only an NVIDIA GPU driver for the
+GPU path. The rest of Jungfraujoch is Linux-only.


 ## Software dependencies