macro_rules! gam_binary {
() => { ... };
}Expand description
Path to the gam CLI binary for tests that shell out to it.
The CLI was peeled off the engine into the crates/gam-cli workspace member
(#1521). Cargo only injects CARGO_BIN_EXE_<name> for integration tests that
live in the same package as the [[bin]], so the root gam package’s
integration targets no longer receive CARGO_BIN_EXE_gam — option_env!
resolves to None at the call site and we must locate the binary at runtime.
The workspace shares one target/ directory, and the CLI binary for a given
profile sits next to the test harness’s own profile directory:
target/<profile>/gam alongside target/<profile>/deps/<test>. Deriving the
path from the running test’s own executable therefore tracks whatever profile
the suite was built under (debug, release, or the quality suite’s
release-dev) instead of hardcoding debug, which only ever existed for the
default cargo test runs and left the optimized quality job unable to spawn
the binary at all.