Hive
feat: Thread cargo build script directives
GitHub issue · Closed
Source
tuist/once #17
Updated
Jun 24, 2026
Domains
Once
Summary
- Thread captured cargo build-script directives into downstream granular Rust
rustcactions. - Represent
cargo_build_scriptnodes as first-class graph deps with real action digests and restored directive output paths. - Move checked-in examples under grouped paths like
examples/rust/granular/basic-appandexamples/apple/ios/simulator-app, with source code and README files in each project. - Add
examples/rust/granular/build-script-cfgfor the build-script scenario, then update shellspec coverage to copy that example into each test workspace and verify cfg propagation, cache hits, and invalidation.
Why
The lower-level TOML graph already allowed [[cargo.build_script]], but dependents did not consume the captured directives. That left build-script-backed crates on the cargo.binary escape hatch even when the graph was declared explicitly.
The build-script scenario is now visible as a normal example project instead of being generated inline inside the shellspec.
Validation
mise exec -- cargo test --workspacemise exec -- cargo fmt --all -- --checkmise exec -- cargo clippy --workspace --all-targets -- -D warningsmise exec -- cargo build --releasemise exec -- shellspec
No GitHub comments yet.