fix(install): add windows scripts entrypoints

This commit is contained in:
VideoTools CI 2026-01-23 06:07:17 -05:00
parent 49becf9c2d
commit 4aebb39297
7 changed files with 34 additions and 16 deletions

View File

@ -32,6 +32,8 @@
- `install.sh` now runs the Windows installer in the same terminal via `winpty` when available. - `install.sh` now runs the Windows installer in the same terminal via `winpty` when available.
- ✅ **Windows root entrypoints** - ✅ **Windows root entrypoints**
- Added `install.bat` and `install.ps1` to avoid Git Bash popping up from PowerShell. - Added `install.bat` and `install.ps1` to avoid Git Bash popping up from PowerShell.
- ✅ **Windows scripts entrypoints**
- Added `scripts/install.ps1` and `scripts/install.bat` to keep the Windows workflow inside PowerShell/CMD.
## Version 0.1.0-dev25 (2026-01-22) - Settings Preferences Expansion ## Version 0.1.0-dev25 (2026-01-22) - Settings Preferences Expansion

View File

@ -18,6 +18,8 @@ This file tracks upcoming features, improvements, and known issues.
- Keep Windows installs in the same Git Bash terminal using `winpty` when available. - Keep Windows installs in the same Git Bash terminal using `winpty` when available.
- [X] **Windows root entrypoints** - [X] **Windows root entrypoints**
- Provide `install.bat` and `install.ps1` for PowerShell-first installs. - Provide `install.bat` and `install.ps1` for PowerShell-first installs.
- [X] **Windows scripts entrypoints**
- Provide `scripts/install.ps1` and `scripts/install.bat` to avoid Git Bash pop-ups.
## Documentation: Fix Structural Errors ## Documentation: Fix Structural Errors

View File

@ -11,7 +11,7 @@ Welcome to the VideoTools installation guide. Please select your operating syste
For Windows 10 and 11, please follow our detailed, step-by-step guide. It covers both automated and manual setup. For Windows 10 and 11, please follow our detailed, step-by-step guide. It covers both automated and manual setup.
- **[➡️ View Windows Installation Guide](./INSTALL_WINDOWS.md)** - **[➡️ View Windows Installation Guide](./INSTALL_WINDOWS.md)**
- Use `install.bat` or `install.ps1` on Windows. - Use `scripts\install.bat` or `scripts\install.ps1` on Windows.
### 🐧 Linux & macOS ### 🐧 Linux & macOS

View File

@ -16,9 +16,8 @@ If you haven't already, download the project files as a ZIP and extract them to
1. Open the project folder in File Explorer. 1. Open the project folder in File Explorer.
2. Choose one of these entrypoints: 2. Choose one of these entrypoints:
- Double-click `install.bat` (recommended). - Run `.\scripts\install.bat` (recommended).
- Run `.\install.ps1` from PowerShell. - Run `.\scripts\install.ps1` from PowerShell.
- Run `scripts\install-windows.ps1` from PowerShell.
3. A terminal window will open and run the PowerShell setup script. This will: 3. A terminal window will open and run the PowerShell setup script. This will:
* **Download FFmpeg:** The script automatically fetches the latest stable version of FFmpeg, which is required for all video operations. * **Download FFmpeg:** The script automatically fetches the latest stable version of FFmpeg, which is required for all video operations.
* **Install Dependencies:** It places the necessary files in the correct directories. * **Install Dependencies:** It places the necessary files in the correct directories.
@ -30,7 +29,7 @@ If you haven't already, download the project files as a ZIP and extract them to
Once the script finishes, you can run the application by double-clicking `run.bat` in the main project folder. Once the script finishes, you can run the application by double-clicking `run.bat` in the main project folder.
> **Note:** `scripts/install.sh` is for Bash shells. From PowerShell, use `install.ps1` to avoid Git Bash popping up. > **Note:** On Windows, use `scripts\install.ps1` or `scripts\install.bat`. Running `scripts\install.sh` from PowerShell will open Git Bash.
--- ---

12
scripts/install.bat Normal file
View File

@ -0,0 +1,12 @@
@echo off
setlocal
chcp 65001 >nul
title VideoTools Windows Installation
echo ========================================================
echo VideoTools Windows Installation
echo ========================================================
echo.
powershell -NoProfile -ExecutionPolicy Bypass -File "%~dp0install.ps1"
exit /b %errorlevel%

9
scripts/install.ps1 Normal file
View File

@ -0,0 +1,9 @@
param()
Write-Host "===============================================================" -ForegroundColor Cyan
Write-Host " VideoTools Windows Installation" -ForegroundColor Cyan
Write-Host "===============================================================" -ForegroundColor Cyan
Write-Host ""
& "$PSScriptRoot\install-deps-windows.ps1"
exit $LASTEXITCODE

View File

@ -105,17 +105,11 @@ echo ""
# Windows uses a dedicated installer to avoid Git Bash/PowerShell chaining. # Windows uses a dedicated installer to avoid Git Bash/PowerShell chaining.
if [ "$IS_WINDOWS" = true ]; then if [ "$IS_WINDOWS" = true ]; then
if command -v winpty &> /dev/null; then echo -e "${YELLOW}NOTICE:${NC} Windows detected."
winpty powershell.exe -NoProfile -ExecutionPolicy Bypass -File "$PROJECT_ROOT/scripts/install-deps-windows.ps1" echo "Run one of these from PowerShell or CMD instead:"
exit $? echo " - $PROJECT_ROOT\\scripts\\install.ps1"
fi echo " - $PROJECT_ROOT\\scripts\\install.bat"
if command -v powershell.exe &> /dev/null; then exit 0
powershell.exe -NoProfile -ExecutionPolicy Bypass -File "$PROJECT_ROOT/scripts/install-deps-windows.ps1"
exit $?
fi
echo -e "${RED}[ERROR]${NC} powershell.exe not found."
echo "Please run: $PROJECT_ROOT\\scripts\\setup-windows.bat"
exit 1
fi fi
# Step 1: Check if Go is installed # Step 1: Check if Go is installed