Repository navigation
v0.3.2
AirPDF 0.3.2
Every platform is compiled ahead of time now: Linux and macOS join Windows, so the reader
starts almost immediately wherever you run it.
Downloads
These builds are unsigned, so the installers are not offered here: SmartScreen and Gatekeeper
would block the first launch, and that reads as a fault in the reader rather than in its
distribution. Use the portable packages instead:
- Windows x64:
AirPDF-win-Portable.zip— unzip anywhere and runAirPdf.exe - macOS arm64 / x64:
AirPDF-osx-<arch>-Portable.zip— unzip and dragAirPDF.appto Applications - Linux x64:
AirPDF-0.3.2-linux-x64.tar.gz
The first launch may still need More info → Run anyway on Windows, or right-click → Open on
macOS. The installers return once a signing certificate is configured.
Startup
- Windows, Linux and macOS builds are all NativeAOT. On Windows that took the time to first
window from 5.0 s to 0.7 s; Linux and macOS share the same runtime and the same cause,
which was JIT compilation spread across Avalonia initialisation, XAML loading and first
layout rather than one slow call. - Downloads follow the build: Windows and macOS ship a Velopack portable package, Linux ships
a tar.gz of the AOT output.
Under the hood
- Each platform is built and gated separately, because Windows says nothing about Linux or
macOS: different toolchains, different native assets. The Linux job installs clang and
zlib1g-dev; macOS uses the Xcode toolchain on the runner. - A release or pull request fails on any AOT warning, on a missing binary, or on an output
that is far larger than expected. A build that lost a reflection path still starts and then
misbehaves at run time, which is how a trimmed build once stopped writing settings.