rayelliott
/
barrier
mirror of https://github.com/debauchee/barrier.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
Open-source KVM software
3,159 Commits 20 Branches 42 Tags 86 MiB
C 55.7%
C++ 42.2%
Objective-C++ 1.1%
CMake 0.8%
Objective-C 0.1%
Go to file
walker0643 649b43c3cc
fix names in readme 		2018-02-07 13:20:08 -05:00
.github rebranding symless/synergy to debauchee/barrier 2018-01-27 16:48:17 -05:00
cmake rebranding symless/synergy to debauchee/barrier 2018-01-27 16:48:17 -05:00
debian rebranding symless/synergy to debauchee/barrier 2018-01-27 16:48:17 -05:00
dist fix installer build. at this point the process is not at all robust..it mainly just works for me. 2018-02-06 20:08:37 -05:00
doc fix execute bit on a lot of files 2018-01-28 17:34:15 -05:00
ext fix execute bit on a lot of files 2018-01-28 17:34:15 -05:00
res update artwork 2018-02-02 19:12:14 -05:00
src fix quotations in for platform build 2018-02-06 17:26:23 -05:00
.gitignore add clean_build_windows.bat to help with win64 builds 2018-01-28 17:32:11 -05:00
Build.properties rebranding symless/synergy to debauchee/barrier 2018-01-27 16:48:17 -05:00
CMakeLists.txt rebranding symless/synergy to debauchee/barrier 2018-01-27 16:48:17 -05:00
ChangeLog Make ready v1.9.0-rc3 2017-05-10 15:29:48 +01:00
LICENSE rebranding symless/synergy to debauchee/barrier 2018-01-27 16:48:17 -05:00
README.md fix names in readme 2018-02-07 13:20:08 -05:00
build_installer_windows.bat fix installer build. at this point the process is not at all robust..it mainly just works for me. 2018-02-06 20:08:37 -05:00
clean_build clean_build: try cmake3 before cmake 2018-02-01 18:42:21 -05:00
clean_build_windows.bat rmdir doesn't set errorlevel but mkdir does and can be used to check for errors up to that point...to a point 2018-02-06 17:13:35 -05:00

README.md

Barrier

Eliminate the barrier between your machines.

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). That's it.

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 give 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 if we use it you will be appropriately credited in the log.