Build omapresent for aarch64 - #426
Open
scottjones wants to merge 1 commit into
Open
scottjones wants to merge 1 commit into
scottjones wants to merge 1 commit into
Conversation
The PKGBUILD withheld the aarch64 claim pending a real build. Built it on Apple Silicon (Asahi, native aarch64): plain qmake6 + make needs no patches, and every dependency including qt6-webengine resolves on Arch Linux ARM. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The PKGBUILD deliberately withheld the aarch64 claim:
It is proven now, so this claims it. No patches, no per-arch sources, no conditionals — the qmake6 + make build needed nothing.
Everything below was done on an Apple Silicon MacBook running Asahi Linux, natively on aarch64 rather than under emulation.
It builds
./bin/build --arch aarch64 --package omapresent, twice from a clean worktree, producing an identical 1,861,744-byte package each time:qt6-webengineresolves on Arch Linux ARM (extra6.11.2-1) and the binary linkslibQt6WebEngineCore.so.6andlibQt6WebEngineQuick.so.6. That Chromium dependency was the most likely reason for this not to work.The package is also complete rather than merely compiling: all nine hicolor icon sizes render through ImageMagick, and the desktop file, four vendored licence files, the agent skill with its reference docs, the theme-refresh hook and
welcome.mdare all present — 55 files, matching the x86_64 layout. Nothing inpackage()turned out to be arch-conditional.It runs
Run from the built package against the system Qt6 libraries. Every library resolves; nothing is missing.
omapresent export --pdfdrives the whole QtWebEngine stack without a display, which makes it the most checkable evidence here:Three slides from three
---separators at the right 16:9 geometry, with Chromium and Skia named as the producer — so the render path executed on ARM rather than merely linking. The rendered output also shows the vendored libraries working: markdown-it parsed the deck, the theme colours applied, and KaTeX typeset$E = mc^2$as real math with a superscript.The GUI works too. Under Hyprland it maps a genuine Wayland surface (
class='omapresent',title='deck.md - Omapresent', 737x926) and shows the live split-pane editor — syntax-highlighted markdown on the left, WebEngine preview on the right, status bar with a live word count.One note for anyone else testing on Asahi: both runs print
libva error: /usr/lib/dri/asahi_drv_video.so init failed. That is Asahi's VA-API hardware video decode failing to initialise, unrelated to this package; Chromium falls back and renders correctly.Unrelated, mentioned rather than fixed here
On a fresh checkout the local
[omarchy]pool underpkgs.omarchy.org/$MIRROR/$ARCHis empty, sottf-ia-writercannot resolve and the build fails — andbin/buildstill exits 0 in that case, reportingBuilt: 0 / Failed: 1alongside a success status. Anything consuming that exit code reads a total failure as green. Worth its own issue; I have kept it out of this diff.🤖 Generated with Claude Code