Supported Platform Routes (Emacsvox User Manual)

Next: Install Omnivox From A Release Binary, Up: Speech Backends [Contents][Index]

4.1 Supported Platform Routes ¶

The following table describes Emacsvox support, not every platform that the Omnivox project can build. “Host check required” means that automated build and archive verification does not prove playback through the user’s audio device; an audible omnivox --check on that machine remains the acceptance test.

Emacs platform	Recommended route	Current support evidence
GNU/Linux x86-64 with an Ubuntu 24.04-compatible runtime	Omnivox 1.4.1 release archive using eSpeak NG	The published archive is built and verified on Ubuntu 24.04. Compatible glibc, libstdc++, libgcc, and ALSA runtime libraries are required; the audible host check remains required.
Other GNU/Linux systems	Source-built Omnivox using eSpeak NG	Use the source route for Linux ARM64, an older distribution ABI, or a host that cannot run the published x86-64 archive.
macOS on Apple silicon	Omnivox 1.4.1 release archive using AVSpeechSynthesizer	The published ARM64 archive is built and verified on a native macOS runner; the audible host check remains required.
macOS on Intel	Omnivox 1.4.1 release archive using AVSpeechSynthesizer	The published x64 archive is built and verified on a native macOS runner; the audible host check remains required.
Emacs in WSL2 on x86-64 Windows	Omnivox 1.4.1 Windows x64 release archive using WinRT	The published archive is checksum-protected and release CI verifies its architecture, adjacent data, WinRT and eSpeak synthesis. The audible host check remains required.
Native Windows Emacs	Omnivox 1.4.1 Windows release using WinRT	Preview. Omnivox verifies its native Windows archive, and Emacsvox can start `omnivox.exe` directly, but the complete combination has not passed a fresh-machine acceptance test. Initial users should use WSL2; evaluators can follow the bounded trial below.

The release-archive routes below are the shortest installation on matching GNU/Linux, macOS, and WSL2 hosts. A bare executable, a repository tag, or an unpackaged CI artifact is not a complete installation: keep the release’s runtime data and notices beside the executable.

Do not set OMNIVOX_ENGINE during initial setup. Its empty value selects the normal platform engine above. Engine routing and optional Piper, Eloquence, or DECtalk support are later customizations, not prerequisites for first speech.