[Feature Request] Add native Linux ARM64 (AArch64) desktop builds
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 47/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- build-system, desktop
Research direction
Start by reading the Linux desktop build and release CI setup referenced in related issue #1553, then trace how existing Linux packages are produced. Check whether the pipeline supports the aarch64-unknown-linux-gnu target and which package formats it publishes. Done means an ARM64 Linux build is published alongside the existing release, with architecture specific limitations documented.
Written by the indexing model from the issue text.
Description
Hi Cap team!
Thanks for bringing native Linux support to Cap in v0.6.1!
I'd like to request official support for Linux ARM64 (AArch64) devices.
Currently, I haven't been able to find an official ARM64 Linux desktop build of Cap. It would be great to have ARM64 packages alongside the existing Linux release.
Linux on ARM64 is increasingly used on ARM-based laptops, development machines, single-board computers, and other devices.
Without a native ARM64 build, users cannot easily install and run the Cap desktop screen recorder on these systems.
Proposed solution
- Add native builds for
aarch64-unknown-linux-gnu. - Publish ARM64 Linux packages, ideally
.deb,.rpm, or AppImage, depending on the supported packaging formats. - Add ARM64 builds to the existing release/CI pipeline.
- Document any architecture-specific limitations, including screen capture or hardware encoding support.
Related issue: #1553 — Linux Desktop App support and build pipeline (closed after Linux support was released in v0.6.1).
This request specifically concerns native ARM64 Linux support rather than general Linux availability.
Thanks for considering this!
- Dominant language
- Rust
- Stars
- 25k
- Forks
- 2.4k
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 676
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CapSoftware/Cap
-
Captions panel does not offer to show an existing transcriptPossibly taken @thedavidweng claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
CapSoftware/Cap#4276 · 1 comment ·
Maintainers usually reply within 1 day
-
Download, FAQ, privacy and terms pages have no meta descriptionPossibly taken @patrickballard claimed this 13 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
CapSoftware/Cap#3675 · 1 comment ·
Maintainers usually reply within 1 day
-
self hosting
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
CapSoftware/Cap#2384 · 3 comments ·
Maintainers usually reply within 1 day
-
Dashboard pagination causes full page reloads on self-hosted CapPossibly taken @DipanshuAmbilkar03 claimed this 11 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
CapSoftware/Cap#2305 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
CapSoftware/Cap#1714 · 3 comments ·
Maintainers usually reply within 1 day
Similar issues
-
benchmark-review
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day
-
area:filesystem bug need-triage
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
libracoder/kiri#364 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
matrix-org/matrix-rust-sdk#7495 ·
Maintainers usually reply within 1 day