Benjamin Carlsson
fc7d34ad67
## Why The pinned voice source inputs can be prepared but do not yet provide compiled native libraries for downstream integration. ## What changed - Add `build_native.py` to build a shared-library prefix for the supported voice dependencies on native x64 and ARM64 GNU/Linux, macOS, and Windows MSVC hosts. - Require explicit toolchain inputs, isolate dependency discovery to the output prefix, and record command logs and build state for provenance and failures. - Expose the recipe and source inputs through `//third_party/voice:build_inputs` and document its prerequisites, outputs, and integration boundaries. ## Testing - `PYTHONSAFEPATH=1 python3 -m unittest discover -s third_party/voice -p 'test_build_native.py'` GitOrigin-RevId: 132d93561a8e1bb178518f1248cf87d031060aae
Native voice source inputs
This stage pins and prepares sources for a privately bundled, GStreamer-based audio runtime, including its native dependencies and build tools. It does not compile native libraries, link them into Codex or enable voice.
sources.json records the versions, URLs and SHA-256 digests of 11 archives:
| Purpose | Sources |
|---|---|
| GStreamer framework and plugin sources | gstreamer, gst-plugins-base, gst-plugins-good |
| Supporting native libraries | glib, libffi, pcre2, zlib, proxy-libintl |
| Audio codec | opus |
| Build tools, not runtime libraries | meson, ninja |
GLib also includes gvdb in its archive; it is recorded without a separate fetch.
These inputs do not include the complete platform toolchain for native builds.
Bazel uses standard http_archive rules to fetch, verify, unpack and cache the
archives from that manifest. Run from the repository root:
bazel build //third_party/voice:sources
For offline preparation without Bazel, use Python 3.12 or newer and an existing archive directory whose filenames match the manifest:
python3 third_party/voice/prepare_sources.py --archives /path/to/archives --output /path/to/new-sources
python3 -m unittest discover -s third_party/voice -p 'test_*.py'
The adapter verifies archive digests and bounds, then extracts with Python's
tarfile data filter. It preserves links where supported and copies their archive
targets when link creation is unavailable, including on Windows. It refuses an
existing output directory and cleans up incomplete output. prepared.json records
successful preparation, not the integrity of later edits to the extracted tree.
Ordinary CLI builds do not run either path. The Bazel :sources target is
manual, so wildcard builds do not fetch these archives. :source_inputs
exports the manifest and adapter for standalone consumers; :sources exposes
extracted archives with Bazel build metadata. Neither target compiles libraries.
Checksums establish input identity, not security or license approval. Native compilation, final Cargo/Bazel linking, installed packages, minimum OS support and duplex audio validation remain separate stages. These inputs do not establish a shared Opus build with Rust consumers or a reduced dependency count.
Rust opus 0.4.0 is available through Socket. Adding Rust transport dependencies
and establishing a shared Opus build remain separate integration work.
Native build recipe
build_native.py runs the unmodified upstream build systems in a new output
directory, using the same archives. Specify the target and existing compiler,
CMake, make, pkg-config and shell paths explicitly. It requires a matching
native host: GNU Linux, macOS, or Windows MSVC, on x64 or ARM64.
On macOS, specify the existing release deployment target with
--deployment-target; the host OS version is not an acceptable default.
Windows requires the normal Visual Studio SDK environment, GNU make and a
POSIX shell for upstream libffi, and --bootstrap-make pointing to NMake.
The recipe does not install these build prerequisites or patch upstream sources.
Outputs are under prefix/, build tools under tools/, and logs beside them.
build-state.json records completed commands and failures; built.json exists
only when every build/install command succeeds. Failed builds retain their logs
and must use a new output directory on retry. CMake compiler-identification logs
and the recorded tool/configuration inputs remain part of the build provenance.
The recipe disables optional plugins and Meson fallback dependency resolution,
with pkg-config restricted to this prefix. Only system ABI libraries/frameworks
may remain external; runtime closure inspection must verify that independently.
//third_party/voice:build_inputs exposes the recipe and source inputs to Bazel.
Neither this filegroup nor a successful prefix build proves final Cargo/Bazel
linkage, safe private runtime loading, or an installed voice-capable Codex package.