Files
ruvnet--RuView/v2
ruv 6fe405a5f7 fix(wasm-edge): gate ghost_hunter bin behind standalone-bin feature
The standalone ghost_hunter binary defines its own on_init/on_frame/on_timer
WASM3 entry-points; the lib also exports those when default-pipeline is on.
A vanilla `cargo build -p wifi-densepose-wasm-edge --target wasm32-unknown-unknown
--release` would build both, producing a "Linking globals named 'on_frame':
symbol multiply defined!" error.

Fix: declare an explicit `[[bin]] required-features = ["standalone-bin"]`
gate so the bin only builds when the user opts in with
`--no-default-features --features standalone-bin`. The default feature
set continues to produce the combined-pipeline lib (15 KB wasm32).

Validation:
- cargo build -p wifi-densepose-wasm-edge --target wasm32-unknown-unknown
  --release  → 15 KB wifi_densepose_wasm_edge.wasm (default-pipeline lib)
- cargo build -p wifi-densepose-wasm-edge --bin ghost_hunter
  --target wasm32-unknown-unknown --release
  --no-default-features --features standalone-bin
  → 5.8 KB ghost_hunter.wasm (standalone module)
- cd v2/crates/wifi-densepose-wasm-edge && cargo test --features std
  --no-default-features  → 75/75 tests pass

Co-Authored-By: claude-flow <ruv@ruv.net>
2026-04-27 11:22:35 -04:00
..