Cargo.toml

# Workspace root, so there is ONE place the cross-compile linker is configured.
#
# Cargo discovers .cargo/config.toml from the CURRENT DIRECTORY, not from --manifest-path. With the
# config living only under engine/, `cargo build --manifest-path engine/Cargo.toml` from here found
# no linker and failed with Apple ld rejecting GNU flags, while the identical build from inside
# engine/ succeeded. That is a trap for CI and for anyone scripting a release, so the workspace and
# the config both live at the root and every invocation resolves the same way.
[workspace]
resolver = "2"
members = ["engine", "mock"]

# Release profile lives here because cargo ignores [profile] in a non-root workspace member and
# warns about it. Carried over verbatim from mock/Cargo.toml, which set it before the workspace
# existed: the mock is on the measurement path, so it is built for speed, not for build time.
[profile.release]
opt-level = 3
lto = true
codegen-units = 1
panic = "abort"