b1f40638d1
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: 1. Not having Inno Setup installed 2. Running build_installer.bat 3. Checked that the error message appears. 4. Installed Inno Setup 6 for my current user 5. Checked that the error message does not appear. 6. Checked that the installer package is generated 6. Uninstalled Inno Setup 6 7. Installed Inno Setup 6 for all users 8. Checked that the error message does not appear. 9. Checked that the installer package is generated 10. Uninstalled Inno Setup 6 11. Installed Inno Setup 5 12. Checked that the error message does not appear. 13. Checked that the installer package is generated |
||
|---|---|---|
| .github | ||
| azure-pipelines | ||
| cmake | ||
| debian | ||
| dist | ||
| doc | ||
| ext | ||
| res | ||
| snap | ||
| src | ||
| .gitignore | ||
| Build.properties | ||
| CMakeLists.txt | ||
| ChangeLog | ||
| LICENSE | ||
| README.md | ||
| _config.yml | ||
| azure-pipelines.yml | ||
| build_installer.bat | ||
| clean_build.bat | ||
| clean_build.sh | ||
| osx_environment.sh | ||
| pre-build.bat | ||
README.md
Barrier
Eliminate the barrier between your machines. Find releases here.
Contact info:
#barrieron freenode
CI Build Status
Master branch overall build status:
- Linux Build Status:
- Mac Build Status:
- Windows Debug Build Status:
- Windows Release Build Status:
Our CI Builds are provided by Microsoft Azure Pipelines.
What is it?
Barrier is KVM software forked from Symless's synergy 1.9 codebase. Synergy was a commercialized reimplementation of the original CosmoSynergy written by Chris Schoeneman.
What's different?
Whereas synergy has moved beyond its goals from the 1.x era, Barrier aims to maintain that simplicity. Barrier will let you use your keyboard and mouse from machine A to control machine B (or more). It's that simple.
Project goals
Hassle-free reliability. We are users, too. Barrier was created so that we could solve the issues we had with synergy and then share these fixes with other users.
Compatibility. We use more than one operating system and you probably do, too. Windows, OSX, Linux, FreeBSD... Barrier should "just work". We will also have our eye on Wayland when the time comes.
Communication. Everything we do is in the open. Our issue tracker will let you see if others are having the same problem you're having and will allow you to add additional information. You will also be able to see when progress is made and how the issue gets resolved.
Contact & support
Please be aware that the only way to draw our attention to a bug is to create a new PR in the issue tracker. Write a clear, concise, detailed report and you will get a clear, concise, detailed response. Priority is always given to issues that affect a wider range of users.
For short and simple questions or to just say hello find us on the Freenode IRC network in the #barrier channel.
Contributions
At this time we are looking for developers to help fix the issues found in the issue tracker. Submit pull requests once you've polished up your patch and we'll review and possibly merge it.
FAQ
Q: Does drag and drop work on linux?
A: No
Q: What OSes are supported?
A:
- Windows 7, 8, 8.1, and 10
- MacOS/OS X
- Linux
- FreeBSD
Q: Are 32-bit versions of Windows supported?
A: No