Benjamin Carlsson
da20788df9
## Why Linux voice needs system ALSA plugins and enough buffering to accommodate PipeWire graph cycles without losing capture samples. Voice startup failures also need actionable diagnostics without exposing native error details. ## What changed - Build and bundle GNU voice helpers and runtimes with primary Linux musl release archives, and sign the archives. Keep Python wheels free of these libraries to preserve `manylinux_2_17` compatibility. - Discover ALSA plugins in fixed system directories and increase Linux capture and playback buffering to support larger PipeWire graph cycles. - Report voice failures by stage, preserve negotiation timeout classification, and discard native error sources. Suppress the misleading `requested` closure message after failure cleanup. - Add explicit Windows MSVC, pkgconf, and CMake toolchain configuration and preserve host architecture in native build environments. ## Testing Add coverage for Linux release assembly, ALSA plugin discovery, PipeWire capture and playback, classified startup failures, failure cleanup rendering, and Windows build environment handling. GitOrigin-RevId: d805eace96a669ce3a4489f12e2db6f68f9f7f53
1.1 KiB
Native voice libraries in Codex releases
Codex release packages with voice include dynamically linked GStreamer and GLib
libraries and selected plugins, plus their native library dependencies. These
components have their own copyrights and licenses. Their notices accompany
this file in licenses/: LGPL-2.1.txt for GStreamer and GLib,
proxy-libintl.txt for libintl, libffi.txt, PCRE2.md and sljit.txt
for PCRE2, Opus.txt, and zlib.txt. GVDB is included with GLib under LGPL.
The exact upstream versions, source archive URLs and SHA-256 digests are in
sources.json alongside this notice. The corresponding build, runtime
projection and package scripts are in the public Codex source tree under
third_party/voice/. The source commit for this package is recorded in
manifest.json. The native libraries remain separate dynamic libraries in
platform-specific runtime directories. Replacements must be compatible with
the package and, on macOS, have valid code signatures. Build tools listed in
sources.json are build inputs, not bundled runtime libraries.