mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #1010] No barrier/barrierc build for pinephone (ARM64 Linux phone) #807
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#807
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?
Originally created by @Utopiah on GitHub (Jan 8, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1010
Describe the bug
I'm trying to get barrier or barrierc on a pinephone, Linux Arm mobile phone with an Alpine based distribution (PostmarketOS). I saw some Alpine x64 or Arm Windows32 but I don't see any Alpine Arm/Aarch64 builds.
Additional context
I naively tried to apk install dependencies but quite a few are missing.
@p12tic commented on GitHub (Jan 10, 2021):
Thanks for the bug report.
Unfortunately we don't create most of the Barrier packages. I think it makes sense to fill a bug report in either Alpine or PostmarketOS depending on which has Barrier already packaged for non-ARM systems. Barrier works on ARM64 already, so it should not be too much work to provide a ARM64 build depending on the tooling that the packagers have.
@Utopiah commented on GitHub (Jan 11, 2021):
Thanks for coming back so fast. I'll check with PostmarketOS first which might eventually backtrack to Alpine repositories. Still in order to expedite the process I imagine skipping Qt could help, hence the suggestion of using first only barrierc. I had a try at the build process and it worked on my Debian machine right away. Unfortunately skimming through I didn't notice any flag that would allow to build just barrierc. Is there a way to do so? Would it actually facilitate or not so much?'''
@p12tic commented on GitHub (Jan 11, 2021):
You can set BARRIER_BUILD_GUI Cmake option to off to disable building of the GUI component. IIRC that would avoid Qt dependency.