mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[PR #400] Check Inno Setup is installed #1621
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#1621
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/debauchee/barrier/pull/400
Author: @MichaelMcDonnell
Created: 8/17/2019
Status: 🔄 Open
Base:
master← Head:check-for-inno-setup📝 Commits (1)
b1f4063Check Inno Setup is installed📊 Changes
1 file changed (+27 additions, -5 deletions)
View changed files
📝
build_installer.bat(+27 -5)📄 Description
The build_installer.bat file uses Inno Setup to build the installer. It
does currently not check if Inno Setup is installed, and fails with the
message:
The system cannot find the path specified.
Build failed
That message does not explain how to fix the problem. I have added a
loop to search for Inno Setup 6 and 5. The user installed Inno Setup is
preferred over the system installed version. If Inno Setup cannot be
found then it prints an actionable error message.
I have tested it by:
NOTE: There is an existing issue where you have to manually terminate barrierd.exe after Quitting Barrier. If you do not do that then the uninstaller will not be able to remove everything. It was reproduced with the latest release version (2.3.1).
Fixes #397
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.