On this page
What the author builtApplication examples in the postAvailability at the timeA useful runtime comparisonOriginal publication: 2025-09-29. English edition and practical reading notes: Linglong editorial, 18 October 2026. Chinese original.
This project-sharing post was published on 29 September 2025 and credited mozixun, linking to the original forum post.
What the author built
The author reported completing a GTK4 runtime inside Linyaps, with source at LFRon/org.deepin.runtime.gtk4. He then spent two days and nights modifying WebKit2GTK and resolving its linking problems; that work was published at LFRon/webkit2gtk-for-linyaps.

Application examples in the post
The first example was Biliup-app. The author explicitly said this was not the AppImage edition and that no runtime libraries were bundled inside the application. The second example was Venera, likewise shown without bundled runtime libraries.




Availability at the time
The post said that the runtime had reached the community’s self-hosted testing repository and invited interested readers to contact the author privately. That invitation belongs to the September 2025 post. It is not an open access credential, a stable-repository guarantee or proof that a given Tauri or Flutter application works on a reader’s machine today.
A useful runtime comparison
A smaller application archive may be relying on a separately installed shared runtime. Compare the complete environment, not only the application’s download size.
- Write down the application ID, exact version, architecture, base and runtime IDs.
- List which GTK/WebKit libraries come from the shared runtime and which files are in the application package.
- Use a disposable target environment to test window creation, required web views, file opening and restart.
- Record the repository/channel and actual result. Do not add a private testing source from an old invitation.
Application ID / version:
CPU / distribution:
Base / shared runtime:
Libraries bundled with the app:
Repository and channel:
Window / web view / file operation / restart:
Observed result:The diagram explains dependency placement; it is not a package-size benchmark.