Repository navigation
A compatibility release. No new features — it fixes two ways 1.0.1 refused to
run on machines it claimed to support.
Both defects had the same shape: the build worked on the machine that produced
it, was unrunnable elsewhere, and nothing in the pipeline could tell.
macOS is now universal
1.0.1 shipped arm64 only. macOS 14 is the deployment target and Sonoma still
runs on the 2018-2020 Intel Macs, so every one of those was excluded by
architecture alone while meeting the stated requirement — and the bundle
assembled, signed and verified anyway.
LiveWall-macos.zip now carries both slices, each at minos 14.0. The x86_64
half was checked under Rosetta. bundle.sh builds both by default and prints
what it produced; LIVEWALL_ARCHS=arm64 restores the fast path for
development.
The macOS floor stays at 14.0. Lowering it needs an API audit and is not part
of this release.
The Linux binary now starts on old distros
1.0.1 would not run on the distro it was built on. AppVeyor's Ubuntu 20.04
image carries GCC 11.4, so the binary referenced GLIBCXX_3.4.29 while stock
focal provides GCC 10's runtime:
./livewall: /usr/lib/x86_64-linux-gnu/libstdc++.so.6:
version `GLIBCXX_3.4.29' not found
The floor was being set by the compiler, not the distro, so building on an old
release bought nothing. libstdc++ and libgcc are now linked statically. glibc
stays dynamic — a static one breaks dlopen and NSS, which this app needs.
The binary went from 411 KB to 529 KB, and its only remaining floor is
glibc 2.25 (2017): Ubuntu 18.04, Debian 10, RHEL 8 and anything newer.
CI now fails if libstdc++ becomes dynamic again or any GLIBCXX_ reference
reappears, and prints the remaining glibc floor on every build. That check is
the actual deliverable — neither defect was visible from the build machine.
Still x86-64 only
Windows and Linux ship for x86-64 alone. Windows on ARM runs the x64 build
under emulation, which works but costs CPU continuously — the one thing this
app is built to avoid. Native ARM64 for both is a known gap, not an oversight.
Unchanged from 1.0.1
Everything else, including what is not verified: no CI runner has a GPU or a
desktop session, so on Windows the WorkerW parenting, Direct3D 11 and Media
Foundation decode paths have still never executed. The Linux Xvfb smoke test
remains the only runtime evidence in this project, and it runs without a render
node, so VA-API is untested.
Android is signed with the same key as 1.0.0 and 1.0.1 and installs over both.
Checksums (SHA-256)
60723aa234878a47d502654f2ad4efd3496fbdd57b74c19eab3c5cef1810e12e LiveWall-macos.zip
cd742a10dc1bf78ea754f702a68406b025367bc0e1917e2cd44b4a9f88378a8a LiveWall.exe
0627ec8860574811da2e323e9915e8049bdda6f05ea3fac0f317d83e0a705f9b livewall
0c6c202e647f1a1c02c1d0140908a42517d75b34bc5a694639056077a4a05718 LiveWall-android.apk