Eglantine daily builds: what each package is
Latest release
daily-20261121prerelease Published 2026-11-21· 12 packages below
Copies a prompt your AI agent can run to install Eglantine.
Which package should I choose?
Every daily names its platform, CPU and build type in the file name: Windows and Linux come in x86_64 and aarch64, macOS in arm64, and names with -pgo are profile-guided builds compiled from the games the team tests. AppImage is the one-file Linux format, the tar.gz the same build as an archive, and macOS offers dmg for installing or zip for carrying. The table below is the newest daily's actual list.
| Package | Architecture | Size |
|---|---|---|
| eglantine-linux-aarch64-pgo.AppImage ↗ | arm64 | 61.8 MB |
| eglantine-linux-aarch64-pgo.tar.gz ↗ | arm64 | 35.2 MB |
| eglantine-linux-aarch64.AppImage ↗ | arm64 | 65.8 MB |
| eglantine-linux-aarch64.tar.gz ↗ | arm64 | 40.4 MB |
| eglantine-linux-x86_64-pgo.AppImage ↗ | x86_64 | 64.5 MB |
| eglantine-linux-x86_64-pgo.tar.gz ↗ | x86_64 | 37.5 MB |
| eglantine-linux-x86_64.AppImage ↗ | x86_64 | 69.4 MB |
| eglantine-linux-x86_64.tar.gz ↗ | x86_64 | 43.6 MB |
| eglantine-macos-arm64.dmg ↗ | arm64 | 83.9 MB |
| eglantine-macos-arm64.zip ↗ | arm64 | 75.7 MB |
| eglantine-windows-x86_64-pgo.zip ↗ | x86_64 | 68.7 MB |
| eglantine-windows-x86_64.zip ↗ | x86_64 | 109.7 MB |
What this build needs
A 64-bit Windows, Linux or macOS machine with current GPU drivers that support Vulkan. Builds are portable: extract and run, no installer. Games, keys and firmware are never part of a package.
Getting started
Prepare your system
Check the GPU driver requirements in the upstream README and install current drivers.
Get the build
Download a release from the official upstream releases page. Every link on our download page points there directly.
Configure
Follow the upstream configuration guide for your platform. The project documents firmware handling for users who dump their own console.
Load a game
Use your own legally obtained game dump. Do not redistribute built game files.
Common problems
-
A daily breaks something that worked yesterday
Dailies are automated builds of the development tree and carry no stability promise. Run the previous day's tag and describe the problem on the project's Discord.
-
No game starts at all
Current Vulkan-capable drivers are a hard requirement, and no package contains games, keys or firmware, so check both before reinstalling.
-
A download is flagged by the browser or Windows
Releases are published straight from the project's CI. Confirm you are on the official Eglantine-Community releases page and read that day's notes before overriding the warning.
How it differs
Eglantine is the line most forks in this catalog descend from: PokeDinner forked it, Lichii builds on it, Hokkaido continues both, and Selevet tunes it for one machine. Pick it for the upstream cadence itself, with changes landing as dailies instead of version numbers.
Recent upstream releases
- Eglantine Build 21/11/2026 ↗ prerelease Published 2026-11-21 · 12 packages
- Eglantine Build 20/11/2026 ↗ prerelease Published 2026-11-20 · 12 packages
- Eglantine Build 19/11/2026 ↗ prerelease Published 2026-11-19 · 12 packages
See every release on the upstream page ↗
Last checked 2026-11-22. Release data fetched 2026-11-22. A release sync refreshes metadata from upstream; it does not re-verify compatibility.
Download FAQ
Why is every Eglantine release marked prerelease?
The project publishes rolling daily builds of its development tree rather than stable versions, and the Discord community does the day-to-day testing.
What is the -pgo package?
A build compiled with profile-guided optimization trained on the games the team plays. It carries the same features as the plain build. Take plain if the name means nothing to you.
Who publishes the dailies?
The project's own GitHub Actions on a schedule. This site links those releases and keeps no copies.
Before installing
- Copy the save folder before switching dailies, since a save one daily wrote may not open in another.
- Read each daily's release notes, which are the only changelog this project keeps.
- Keep a working daily around when you try a new one, so a bad day costs nothing.