github Eglantine-Community/Eglantine build-119
Eglantine nx2-experimental build 119 (2a80edb)

pre-release20 days ago

What's new in this build

This is build 119 of nx2-experimental (2a80edb). It is build 116 plus one fix: the .nup reader. Only src/core/file_sys/nup_container.cpp changed, so nothing else in the emulator behaves differently from 116.

.nup containers written in the NUP v1 layout now open

The .nup loader added in build 110 described the container's records with their fields in the wrong order: the package record read meta_offset and meta_size four bytes early, and the file record kept a stray reserved word after the name and put the size, the two extent fields and the SHA-256 in the wrong slots. A container written in the aligned NUP v1 layout was therefore misread — the file table came back with wrong sizes and offsets, and the per-package metadata that supplies the title name, icon and display version was taken from the wrong bytes.

The record layouts now match NUP v1 exactly, and offsetof assertions pin every field, so a later change to the structs fails to compile instead of silently shifting the format again.

Everything else about .nup is as build 110 described it: base program with the newest update inside the container layered over it, name/icon/version read from the container, add-on content recognised but not mounted, and a malformed container rejected with a message instead of a crash.

Coming from build 116?

Nothing else moved. The same .nup fix is in the nx2 builds 117 and 120. Build 118 has no release — the numbers are CI run ids and they skip when a run fails or is cancelled.

How it works, for the technically curious

  • PackageRecord is 0x40 bytes inside #pragma pack(push, 1): title_id 0x00, root_dir 0x08, exefs_dir 0x0C, romfs_dir 0x10, version 0x14, kind 0x18, flags 0x19, reserved 0x1A, reserved2 0x1C, meta_offset 0x20, meta_size 0x28, reserved3 0x2C. The old struct put meta_offset at 0x1C and meta_size at 0x24.
  • FileRecord is 0x50 bytes packed: name 0x00/0x04, size 0x08, extent_offset 0x10, extent_size 0x18, sha256 0x20, codec 0x40, codec_flags 0x41, reserved2 0x42, reserved3 (12 bytes) 0x44. The old struct had a stray reserved word at 0x08, size at 0x0C, the hash at 0x14 and the extents at 0x34/0x3C.
  • Both structs are packed, so the static_assert(sizeof(...)) checks that already existed could not catch the field reordering — the sizes came out the same. The new static_assert(offsetof(...)) lines can.

Automatic build of nx2-experimental at 2a80edb.

Windows: extract the zip and run eglantine.exe, or eden-cli.exe from a terminal.
Linux (AppImage): make it executable (chmod +x) and run it; it bundles its libraries and needs glibc 2.39 or newer (Ubuntu 24.04, Fedora 40, Debian 13, Arch).
Linux (tar.gz): extract it and run ./eglantine or ./eden-cli; it uses your system libraries, so Qt 6 and the usual libraries must be installed.
macOS: Apple Silicon and macOS 15 or newer. Unzip and move eglantine.app to Applications; eden-cli is inside it, in Contents/MacOS. The app is not notarized, so the first time right-click it and choose Open (or run xattr -dr com.apple.quarantine eglantine.app).
The -pgo builds are the same programs compiled with profile-guided optimization (clang plus Eden's profile); prefer them when your CPU supports it. The Windows PGO build is a MinGW build, so it carries its own DLLs and needs no Visual C++ redistributable.

Don't miss a new Eglantine release

NewReleases is sending notifications on new releases.