[GH-ISSUE #41] Installing on Raspberry Pi? #31

Closed
opened 2026-05-05 04:48:40 -06:00 by gitea-mirror · 9 comments
Owner

Originally created by @clay53 on GitHub (May 21, 2018).
Original GitHub issue: https://github.com/debauchee/barrier/issues/41

Operating Systems

Server: Windows 10

Client: Raspbian Stretch

Barrier Version

2.1.0

Steps to reproduce bug

Try

Other info

  • When did the problem start to occur? When I tried to install it
  • Is there a way to work around it? No/Yes, you can if you know how to
  • Does this bug prevent you from using Barrier entirely? Yes

Put anything else you can think of here.

I can't seem to figure out how to install this on Debian/Raspberry Pi/ARM Linux. Whenever I attempt to use the files is ./bin I get cannot execute binary file: Exec format error. Maybe I'm incompetent, but I just can't seem to get this to work. Whenever I try to search for it I get things about barriers instead of this.

Originally created by @clay53 on GitHub (May 21, 2018). Original GitHub issue: https://github.com/debauchee/barrier/issues/41 ### Operating Systems ### Server: Windows 10 Client: Raspbian Stretch ### Barrier Version ### 2.1.0 ### Steps to reproduce bug ### Try ### Other info ### * When did the problem start to occur? When I tried to install it * Is there a way to work around it? No/Yes, you can if you know how to * Does this bug prevent you from using Barrier entirely? Yes Put anything else you can think of here. I can't seem to figure out how to install this on Debian/Raspberry Pi/ARM Linux. Whenever I attempt to use the files is ./bin I get cannot execute binary file: Exec format error. Maybe I'm incompetent, but I just can't seem to get this to work. Whenever I try to search for it I get things about barriers instead of this.
Author
Owner

@walker0643 commented on GitHub (May 25, 2018):

Hi @clay53 - it sounds like you're attempting to run a Barrier build from another platform. When you installed it did you use a precompiled package for another Linux (non-ARM, perhaps?) or did you compile it natively yourself?

<!-- gh-comment-id:392142073 --> @walker0643 commented on GitHub (May 25, 2018): Hi @clay53 - it sounds like you're attempting to run a Barrier build from another platform. When you installed it did you use a precompiled package for another Linux (non-ARM, perhaps?) or did you compile it natively yourself?
Author
Owner

@clay53 commented on GitHub (May 26, 2018):

I used the precompiled Linux package I was hoping it was universal (ARM & x86), but maybe not.

<!-- gh-comment-id:392218735 --> @clay53 commented on GitHub (May 26, 2018): I used the precompiled Linux package I was hoping it was universal (ARM & x86), but maybe not.
Author
Owner

@clay53 commented on GitHub (May 26, 2018):

If I do need to compile it myself, how would I did that?

<!-- gh-comment-id:392218845 --> @clay53 commented on GitHub (May 26, 2018): If I do need to compile it myself, how would I did that?
Author
Owner

@dayne commented on GitHub (May 29, 2018):

@clay53 the Raspberry Pi is an ARM based processor meaning it can't directly use binaries built for x86. You'll need to build it up.

Here are the instructions I think should work for you on latest Raspbian Stretch:

sudo apt update && sudo apt upgrade
sudo apt install git cmake make xorg-dev g++ libcurl4-openssl-dev \
                 libavahi-compat-libdnssd-dev libssl-dev libx11-dev \
                 libqt4-dev qtbase5-dev
git clone https://github.com/debauchee/barrier.git
cd barrier
cmake .
make

Somebody with wiki editing permissions might consider adding these steps to the wiki at: https://github.com/debauchee/barrier/wiki/Building-on-Linux

<!-- gh-comment-id:392900982 --> @dayne commented on GitHub (May 29, 2018): @clay53 the Raspberry Pi is an ARM based processor meaning it can't directly use binaries built for x86. You'll need to build it up. Here are the instructions I think should work for you on latest Raspbian Stretch: ``` sudo apt update && sudo apt upgrade sudo apt install git cmake make xorg-dev g++ libcurl4-openssl-dev \ libavahi-compat-libdnssd-dev libssl-dev libx11-dev \ libqt4-dev qtbase5-dev git clone https://github.com/debauchee/barrier.git cd barrier cmake . make ``` Somebody with wiki editing permissions might consider adding these steps to the wiki at: https://github.com/debauchee/barrier/wiki/Building-on-Linux
Author
Owner

@dayne commented on GitHub (May 29, 2018):

To follow up - there might be more issues here. The build on the RPi did succeed and I was able to launch barrier, configure it, and exchange (trust) SSL certs. However it didn't actually work correctly.

  • Barrier 2.1.0 on Windows as the server.
  • Barrier from Git (master) as of today 773a0081e3

Result when client (rpi) was connected was the mouse didn't move or have effect on either system. When client disconnected mouse control on windows box resumed working.

The only messages in the logs that appear relevant are on the client (RPi) side:

See the following details from the RPI DEBUG2 log:

[2018-05-29T12:14:29] DEBUG2: can't read property 530 on window 0x01200730
[2018-05-29T12:14:29] DEBUG2: can't read property 530 on window 0x01200731
[2018-05-29T12:14:29] DEBUG2: can't read property 530 on window 0x01200732
[2018-05-29T12:14:29] DEBUG2: can't read property 530 on window 0x01200733
[2018-05-29T12:14:29] DEBUG2: can't read property 530 on window 0x01200734
[2018-05-29T12:14:30] DEBUG2: reading secure socket
[2018-05-29T12:14:30] DEBUG2: reading secure socket
[2018-05-29T12:14:30] DEBUG2: want to read, error=2, attempt=1
[2018-05-29T12:14:30] DEBUG2: msg from server: CALV
[2018-05-29T12:14:30] DEBUG2: writef(CALV)
[2018-05-29T12:14:30] DEBUG2: writing secure socket:0x86f200
[2018-05-29T12:14:30] DEBUG2: writing secure socket:0x86f200
[2018-05-29T12:14:30] DEBUG2: wrote 4 bytes
[2018-05-29T12:14:30] DEBUG2: writef(CNOP)
[2018-05-29T12:14:30] DEBUG2: writing secure socket:0x86f200
[2018-05-29T12:14:30] DEBUG2: writing secure socket:0x86f200
[2018-05-29T12:14:30] DEBUG2: wrote 4 bytes
[2018-05-29T12:14:31] DEBUG2: can't read property 530 on window 0x01200742
[2018-05-29T12:14:31] DEBUG2: can't read property 530 on window 0x01200743
[2018-05-29T12:14:31] DEBUG2: can't read property 530 on window 0x01200744
[2018-05-29T12:14:31] DEBUG2: can't read property 530 on window 0x01200745
[2018-05-29T12:14:31] DEBUG2: can't read property 530 on window 0x01200746
[2018-05-29T12:14:31] DEBUG2: can't read property 530 on window 0x01200747
[2018-05-29T12:14:31] DEBUG2: can't read property 530 on window 0x01200748
[2018-05-29T12:14:31] DEBUG2: can't read property 530 on window 0x01200749
[2018-05-29T12:14:33] DEBUG2: reading secure socket
[2018-05-29T12:14:33] DEBUG2: reading secure socket
[2018-05-29T12:14:33] DEBUG2: want to read, error=2, attempt=1
[2018-05-29T12:14:33] DEBUG2: msg from server: CALV
[2018-05-29T12:14:33] DEBUG2: writef(CALV)
[2018-05-29T12:14:33] DEBUG2: writing secure socket:0x86f200
[2018-05-29T12:14:33] DEBUG2: writing secure socket:0x86f200
[2018-05-29T12:14:33] DEBUG2: wrote 4 bytes
[2018-05-29T12:14:33] DEBUG2: writef(CNOP)
[2018-05-29T12:14:33] DEBUG2: writing secure socket:0x86f200
[2018-05-29T12:14:33] DEBUG2: writing secure socket:0x86f200
[2018-05-29T12:14:33] DEBUG2: wrote 4 bytes
[2018-05-29T12:14:36] DEBUG2: reading secure socket
[2018-05-29T12:14:36] DEBUG2: reading secure socket
[2018-05-29T12:14:36] DEBUG2: want to read, error=2, attempt=1
[2018-05-29T12:14:36] DEBUG2: msg from server: CALV
[2018-05-29T12:14:36] DEBUG2: writef(CALV)
[2018-05-29T12:14:36] DEBUG2: writing secure socket:0x86f200
[2018-05-29T12:14:36] DEBUG2: writing secure socket:0x86f200
[2018-05-29T12:14:36] DEBUG2: wrote 4 bytes
[2018-05-29T12:14:36] DEBUG2: writef(CNOP)
[2018-05-29T12:14:36] DEBUG2: writing secure socket:0x86f200
[2018-05-29T12:14:36] DEBUG2: writing secure socket:0x86f200
[2018-05-29T12:14:36] DEBUG2: wrote 4 bytes
[2018-05-29T12:14:39] DEBUG2: reading secure socket
[2018-05-29T12:14:39] DEBUG2: reading secure socket
[2018-05-29T12:14:39] DEBUG2: want to read, error=2, attempt=1
[2018-05-29T12:14:39] DEBUG2: msg from server: CALV
[2018-05-29T12:14:39] DEBUG2: writef(CALV)
[2018-05-29T12:14:39] DEBUG2: writing secure socket:0x86f200
[2018-05-29T12:14:39] DEBUG2: writing secure socket:0x86f200
[2018-05-29T12:14:39] DEBUG2: wrote 4 bytes
[2018-05-29T12:14:39] DEBUG2: writef(CNOP)
[2018-05-29T12:14:39] DEBUG2: writing secure socket:0x86f200
[2018-05-29T12:14:39] DEBUG2: writing secure socket:0x86f200
[2018-05-29T12:14:39] DEBUG2: wrote 4 bytes
[2018-05-29T12:14:42] DEBUG2: reading secure socket
[2018-05-29T12:14:42] DEBUG2: reading secure socket
[2018-05-29T12:14:42] DEBUG2: want to read, error=2, attempt=1
[2018-05-29T12:14:42] DEBUG2: msg from server: CALV
[2018-05-29T12:14:42] DEBUG2: writef(CALV)
[2018-05-29T12:14:42] DEBUG2: wrote 4 bytes
[2018-05-29T12:14:42] DEBUG2: writef(CNOP)
[2018-05-29T12:14:42] DEBUG2: wrote 4 bytes
[2018-05-29T12:14:42] DEBUG2: writing secure socket:0x86f200
[2018-05-29T12:14:45] DEBUG2: reading secure socket
[2018-05-29T12:14:45] DEBUG2: reading secure socket
[2018-05-29T12:14:45] DEBUG2: want to read, error=2, attempt=1
[2018-05-29T12:14:45] DEBUG2: msg from server: CALV
[2018-05-29T12:14:45] DEBUG2: writef(CALV)
[2018-05-29T12:14:45] DEBUG2: writing secure socket:0x86f200
[2018-05-29T12:14:45] DEBUG2: writing secure socket:0x86f200
[2018-05-29T12:14:45] DEBUG2: wrote 4 bytes
[2018-05-29T12:14:45] DEBUG2: writef(CNOP)
[2018-05-29T12:14:45] DEBUG2: writing secure socket:0x86f200
[2018-05-29T12:14:45] DEBUG2: writing secure socket:0x86f200
[2018-05-29T12:14:45] DEBUG2: wrote 4 bytes
[2018-05-29T12:14:46] DEBUG2: can't read property 530 on window 0x01200764
[2018-05-29T12:14:46] DEBUG2: can't read property 530 on window 0x01200765
[2018-05-29T12:14:46] DEBUG2: can't read property 530 on window 0x01200766
[2018-05-29T12:14:46] DEBUG2: can't read property 530 on window 0x01200767
[2018-05-29T12:14:46] DEBUG2: can't read property 530 on window 0x01200768
[2018-05-29T12:14:46] DEBUG2: can't read property 530 on window 0x01200769
[2018-05-29T12:14:46] DEBUG2: can't read property 530 on window 0x0120076a
[2018-05-29T12:14:46] DEBUG2: can't read property 530 on window 0x0120076b
[2018-05-29T12:14:46] DEBUG: stopping process
[2018-05-29T12:14:46] INFO: stopping barrier desktop process
[2018-05-29T12:14:48] DEBUG2: reading secure socket
[2018-05-29T12:14:48] DEBUG2: reading secure socket
[2018-05-29T12:14:48] DEBUG2: want to read, error=2, attempt=1
[2018-05-29T12:14:48] DEBUG2: msg from server: CALV
[2018-05-29T12:14:48] DEBUG2: writef(CALV)
[2018-05-29T12:14:48] DEBUG2: writing secure socket:0x86f200
[2018-05-29T12:14:48] DEBUG2: writing secure socket:0x86f200
[2018-05-29T12:14:48] DEBUG2: wrote 4 bytes
[2018-05-29T12:14:48] DEBUG2: writef(CNOP)
[2018-05-29T12:14:48] DEBUG2: writing secure socket:0x86f200
[2018-05-29T12:14:48] DEBUG2: writing secure socket:0x86f200
[2018-05-29T12:14:48] DEBUG2: wrote 4 bytes
[2018-05-29T12:14:48] DEBUG1: stopping client
[2018-05-29T12:14:48] INFO: leaving screen
[2018-05-29T12:14:48] DEBUG2: mapping state: 0
[2018-05-29T12:14:48] DEBUG: Closing socket: 00842770
[2018-05-29T12:14:48] DEBUG: adopting new buffer
[2018-05-29T12:14:48] DEBUG: discarding 5 event(s)
[2018-05-29T12:14:48] DEBUG: closed display
[2018-05-29T12:14:48] NOTE: stopped client
[2018-05-29T12:14:48] DEBUG1: caught cancel on thread 0x00000002
[2018-05-29T12:14:48] INFO: process exited normally
<!-- gh-comment-id:392930661 --> @dayne commented on GitHub (May 29, 2018): To follow up - there might be more issues here. The build on the RPi did succeed and I was able to launch barrier, configure it, and exchange (trust) SSL certs. However it didn't actually work correctly. * Barrier 2.1.0 on Windows as the server. * Barrier from Git (master) as of today 773a0081e3069f3aadf726830332879f02d84a3b Result when client (rpi) was connected was the mouse didn't move or have effect on either system. When client disconnected mouse control on windows box resumed working. The only messages in the logs that appear relevant are on the client (RPi) side: See the following details from the RPI DEBUG2 log: <details> ``` [2018-05-29T12:14:29] DEBUG2: can't read property 530 on window 0x01200730 [2018-05-29T12:14:29] DEBUG2: can't read property 530 on window 0x01200731 [2018-05-29T12:14:29] DEBUG2: can't read property 530 on window 0x01200732 [2018-05-29T12:14:29] DEBUG2: can't read property 530 on window 0x01200733 [2018-05-29T12:14:29] DEBUG2: can't read property 530 on window 0x01200734 [2018-05-29T12:14:30] DEBUG2: reading secure socket [2018-05-29T12:14:30] DEBUG2: reading secure socket [2018-05-29T12:14:30] DEBUG2: want to read, error=2, attempt=1 [2018-05-29T12:14:30] DEBUG2: msg from server: CALV [2018-05-29T12:14:30] DEBUG2: writef(CALV) [2018-05-29T12:14:30] DEBUG2: writing secure socket:0x86f200 [2018-05-29T12:14:30] DEBUG2: writing secure socket:0x86f200 [2018-05-29T12:14:30] DEBUG2: wrote 4 bytes [2018-05-29T12:14:30] DEBUG2: writef(CNOP) [2018-05-29T12:14:30] DEBUG2: writing secure socket:0x86f200 [2018-05-29T12:14:30] DEBUG2: writing secure socket:0x86f200 [2018-05-29T12:14:30] DEBUG2: wrote 4 bytes [2018-05-29T12:14:31] DEBUG2: can't read property 530 on window 0x01200742 [2018-05-29T12:14:31] DEBUG2: can't read property 530 on window 0x01200743 [2018-05-29T12:14:31] DEBUG2: can't read property 530 on window 0x01200744 [2018-05-29T12:14:31] DEBUG2: can't read property 530 on window 0x01200745 [2018-05-29T12:14:31] DEBUG2: can't read property 530 on window 0x01200746 [2018-05-29T12:14:31] DEBUG2: can't read property 530 on window 0x01200747 [2018-05-29T12:14:31] DEBUG2: can't read property 530 on window 0x01200748 [2018-05-29T12:14:31] DEBUG2: can't read property 530 on window 0x01200749 [2018-05-29T12:14:33] DEBUG2: reading secure socket [2018-05-29T12:14:33] DEBUG2: reading secure socket [2018-05-29T12:14:33] DEBUG2: want to read, error=2, attempt=1 [2018-05-29T12:14:33] DEBUG2: msg from server: CALV [2018-05-29T12:14:33] DEBUG2: writef(CALV) [2018-05-29T12:14:33] DEBUG2: writing secure socket:0x86f200 [2018-05-29T12:14:33] DEBUG2: writing secure socket:0x86f200 [2018-05-29T12:14:33] DEBUG2: wrote 4 bytes [2018-05-29T12:14:33] DEBUG2: writef(CNOP) [2018-05-29T12:14:33] DEBUG2: writing secure socket:0x86f200 [2018-05-29T12:14:33] DEBUG2: writing secure socket:0x86f200 [2018-05-29T12:14:33] DEBUG2: wrote 4 bytes [2018-05-29T12:14:36] DEBUG2: reading secure socket [2018-05-29T12:14:36] DEBUG2: reading secure socket [2018-05-29T12:14:36] DEBUG2: want to read, error=2, attempt=1 [2018-05-29T12:14:36] DEBUG2: msg from server: CALV [2018-05-29T12:14:36] DEBUG2: writef(CALV) [2018-05-29T12:14:36] DEBUG2: writing secure socket:0x86f200 [2018-05-29T12:14:36] DEBUG2: writing secure socket:0x86f200 [2018-05-29T12:14:36] DEBUG2: wrote 4 bytes [2018-05-29T12:14:36] DEBUG2: writef(CNOP) [2018-05-29T12:14:36] DEBUG2: writing secure socket:0x86f200 [2018-05-29T12:14:36] DEBUG2: writing secure socket:0x86f200 [2018-05-29T12:14:36] DEBUG2: wrote 4 bytes [2018-05-29T12:14:39] DEBUG2: reading secure socket [2018-05-29T12:14:39] DEBUG2: reading secure socket [2018-05-29T12:14:39] DEBUG2: want to read, error=2, attempt=1 [2018-05-29T12:14:39] DEBUG2: msg from server: CALV [2018-05-29T12:14:39] DEBUG2: writef(CALV) [2018-05-29T12:14:39] DEBUG2: writing secure socket:0x86f200 [2018-05-29T12:14:39] DEBUG2: writing secure socket:0x86f200 [2018-05-29T12:14:39] DEBUG2: wrote 4 bytes [2018-05-29T12:14:39] DEBUG2: writef(CNOP) [2018-05-29T12:14:39] DEBUG2: writing secure socket:0x86f200 [2018-05-29T12:14:39] DEBUG2: writing secure socket:0x86f200 [2018-05-29T12:14:39] DEBUG2: wrote 4 bytes [2018-05-29T12:14:42] DEBUG2: reading secure socket [2018-05-29T12:14:42] DEBUG2: reading secure socket [2018-05-29T12:14:42] DEBUG2: want to read, error=2, attempt=1 [2018-05-29T12:14:42] DEBUG2: msg from server: CALV [2018-05-29T12:14:42] DEBUG2: writef(CALV) [2018-05-29T12:14:42] DEBUG2: wrote 4 bytes [2018-05-29T12:14:42] DEBUG2: writef(CNOP) [2018-05-29T12:14:42] DEBUG2: wrote 4 bytes [2018-05-29T12:14:42] DEBUG2: writing secure socket:0x86f200 [2018-05-29T12:14:45] DEBUG2: reading secure socket [2018-05-29T12:14:45] DEBUG2: reading secure socket [2018-05-29T12:14:45] DEBUG2: want to read, error=2, attempt=1 [2018-05-29T12:14:45] DEBUG2: msg from server: CALV [2018-05-29T12:14:45] DEBUG2: writef(CALV) [2018-05-29T12:14:45] DEBUG2: writing secure socket:0x86f200 [2018-05-29T12:14:45] DEBUG2: writing secure socket:0x86f200 [2018-05-29T12:14:45] DEBUG2: wrote 4 bytes [2018-05-29T12:14:45] DEBUG2: writef(CNOP) [2018-05-29T12:14:45] DEBUG2: writing secure socket:0x86f200 [2018-05-29T12:14:45] DEBUG2: writing secure socket:0x86f200 [2018-05-29T12:14:45] DEBUG2: wrote 4 bytes [2018-05-29T12:14:46] DEBUG2: can't read property 530 on window 0x01200764 [2018-05-29T12:14:46] DEBUG2: can't read property 530 on window 0x01200765 [2018-05-29T12:14:46] DEBUG2: can't read property 530 on window 0x01200766 [2018-05-29T12:14:46] DEBUG2: can't read property 530 on window 0x01200767 [2018-05-29T12:14:46] DEBUG2: can't read property 530 on window 0x01200768 [2018-05-29T12:14:46] DEBUG2: can't read property 530 on window 0x01200769 [2018-05-29T12:14:46] DEBUG2: can't read property 530 on window 0x0120076a [2018-05-29T12:14:46] DEBUG2: can't read property 530 on window 0x0120076b [2018-05-29T12:14:46] DEBUG: stopping process [2018-05-29T12:14:46] INFO: stopping barrier desktop process [2018-05-29T12:14:48] DEBUG2: reading secure socket [2018-05-29T12:14:48] DEBUG2: reading secure socket [2018-05-29T12:14:48] DEBUG2: want to read, error=2, attempt=1 [2018-05-29T12:14:48] DEBUG2: msg from server: CALV [2018-05-29T12:14:48] DEBUG2: writef(CALV) [2018-05-29T12:14:48] DEBUG2: writing secure socket:0x86f200 [2018-05-29T12:14:48] DEBUG2: writing secure socket:0x86f200 [2018-05-29T12:14:48] DEBUG2: wrote 4 bytes [2018-05-29T12:14:48] DEBUG2: writef(CNOP) [2018-05-29T12:14:48] DEBUG2: writing secure socket:0x86f200 [2018-05-29T12:14:48] DEBUG2: writing secure socket:0x86f200 [2018-05-29T12:14:48] DEBUG2: wrote 4 bytes [2018-05-29T12:14:48] DEBUG1: stopping client [2018-05-29T12:14:48] INFO: leaving screen [2018-05-29T12:14:48] DEBUG2: mapping state: 0 [2018-05-29T12:14:48] DEBUG: Closing socket: 00842770 [2018-05-29T12:14:48] DEBUG: adopting new buffer [2018-05-29T12:14:48] DEBUG: discarding 5 event(s) [2018-05-29T12:14:48] DEBUG: closed display [2018-05-29T12:14:48] NOTE: stopped client [2018-05-29T12:14:48] DEBUG1: caught cancel on thread 0x00000002 [2018-05-29T12:14:48] INFO: process exited normally ``` </details>
Author
Owner

@dayne commented on GitHub (Jun 4, 2018):

The issue I saw after a build on a pi sounds like #42

<!-- gh-comment-id:394488336 --> @dayne commented on GitHub (Jun 4, 2018): The issue I saw after a build on a pi sounds like #42
Author
Owner

@walker0643 commented on GitHub (Jun 30, 2018):

Closing because the original issue is not a bug.

<!-- gh-comment-id:401557094 --> @walker0643 commented on GitHub (Jun 30, 2018): Closing because the original issue is not a bug.
Author
Owner

@jswhisperer commented on GitHub (Jun 3, 2021):

would be nice to have this https://github.com/debauchee/barrier/issues/41#issuecomment-392900982
and this https://github.com/debauchee/barrier/issues/805#issuecomment-660713462
in the docs unless i missed it?

<!-- gh-comment-id:854112761 --> @jswhisperer commented on GitHub (Jun 3, 2021): would be nice to have this https://github.com/debauchee/barrier/issues/41#issuecomment-392900982 and this https://github.com/debauchee/barrier/issues/805#issuecomment-660713462 in the docs unless i missed it?
Author
Owner

@dayne commented on GitHub (Jun 4, 2021):

would be nice to have this #41 (comment)
and this #805 (comment)
in the docs unless i missed it?

The instructions are on the Building-on-Linux wiki page -- just broken up into different chunks. If you downloaded the package instead of cloning the git repo then you should be able to skip the git commands (haven't tested that though)

<!-- gh-comment-id:854484889 --> @dayne commented on GitHub (Jun 4, 2021): > would be nice to have this [#41 (comment)](https://github.com/debauchee/barrier/issues/41#issuecomment-392900982) > and this [#805 (comment)](https://github.com/debauchee/barrier/issues/805#issuecomment-660713462) > in the docs unless i missed it? The instructions are on the [Building-on-Linux](https://github.com/debauchee/barrier/wiki/Building-on-Linux) wiki page -- just broken up into different chunks. If you downloaded the package instead of cloning the git repo then you _should_ be able to skip the git commands (_haven't tested that though_)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/barrier#31
No description provided.