Provide an official Meson consumer recipe and incremental C/C++/Rust integration tests

Abierto
  • ¿Algo no está bien?
#184 0 comentarios 0 reacciones 1 asignado Ver en GitHub

@LunaStev ya está trabajando en esto.

Desde el 2/11/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

Planned for v0.0.3-beta; reviewed against master cd13f1d9c244cfdb207f38412db6c513bd5fd543.

Vex's own Meson automation does not yet document and test consuming an arbitrary Wave package from an external mixed-language Meson project. Provide a small stable consumer path for Whale and similar projects.

Acceptance:

  • Supply a minimal documented Meson example/adapter using Vex's external build root, depfile, result-manifest and object-library settings. Consume machine-readable results rather than human logs or guessed artifact names.
  • Build a real multi-file Wave package with transitive imports and link it to small C, C++ extern-C and Rust C ABI callers. Meson/the language toolchains own foreign compilation and final composition.
  • Cover initial build, no-change build, source/import/config/compiler changes, two independent build roots, read-only prepared source, and locked/offline execution.
  • Verify failure/cancellation preserves the last complete result and propagates a failing status. Cover spaces/Unicode and per-target/profile/feature separation.
  • Publish clear source/build/host/output-target boundaries. Keep compiler capability prerequisites explicit; actual execution evidence is required for each claimed host.
  • Add suitable integration CI without weakening existing nine-host Vex release gates. Include a pinned Whale-shaped freestanding/PIC fixture; actual Whale compiler migration/source restructuring remains in Whale.

Depends on the external-build integration issues in this batch. Existing #66 and #159 compiler/C ABI acceptance remain in place. No Vex SDK, foreign build-script hooks, or replacement build system is required.

Starting points: existing ABI acceptance, project workflows, Vex's own Meson automation.

Integration dependencies: #177, #178, #179, #180, #181, #182, #183.

Lenguaje dominante
Rust
Estrellas
1
Forks
3
Merge medio
23 h 3 min
PR fusionados (30 d)
7

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de wavefnd/Vex

Todos los issues de wavefnd/Vex

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.