From 26b378e7e90f950e8d64a294e56fbe9e06d19214 Mon Sep 17 00:00:00 2001 From: _ov4 Date: Tue, 13 Oct 2026 05:07:14 +0000 Subject: feat: add a per-user PowerShell installer Co-Authored-By: Claude Fable 5.1 --- README.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) (limited to 'README.md') diff --git a/README.md b/README.md index bcaf0ea..4f14498 100644 --- a/README.md +++ b/README.md @@ -194,6 +194,23 @@ For a custom prefix, add its `bin` directory to PATH; `man` normally discovers t adjacent `share/man` directory from PATH. If your man configuration overrides this, use `man -M "$HOME/.local/share/man" cpsc` for the local prefix. +On Windows, `install.ps1` installs for the current user without administrator +rights. Its source directory must contain `cpsc.exe` and `doc/cpsc.html`: + +```powershell +powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\install.ps1 -SourceDir .\build +``` + +The default destination is `%LOCALAPPDATA%\Programs\cpsc`: `cpsc.exe` goes in +that directory and the HTML manual goes in its `doc` subdirectory. The installer +adds the directory to the user PATH and creates Start Menu > cpsc > cpsc Help, +which opens the manual in the default browser. Open a new terminal afterward; +existing parent terminals retain their old PATH. Reinstalling does not duplicate +the PATH entry. Use `-Prefix 'D:\My Programs\cpsc'` for a custom destination, +or `-Help` for usage. Windows installation does not support `DESTDIR` staging. +The PowerShell installer targets Windows PowerShell 5.1 or later and has only +been reviewed statically; Windows installation still needs testing on Windows. + # Note DO NOT OPEN ANY ISSUES IF YOU COMPILE WITH VISUAL STUDIO OR ANYTHING EXCEPT MINGW-W64 (EVEN WITH MINGW-W64, WINDOWS IS LIKELY TO BE A PROBLEM MAKER) -- cgit v1.3.1-4-g156e