Support setting target runner
in the [profile]
settings
#13737
Labels
A-configuration
Area: cargo config files and env vars
A-profiles
Area: profiles
C-bug
Category: bug
S-needs-design
Status: Needs someone to work further on the design for the feature or fix. NOT YET accepted.
Problem
I need to have different runners based on release/debug build
for now
[target.'cfg(debug_assertions)'.runner]
is always active even if--print=cfg
shows nodebug_assertions
. I'm aware of the docs mentioning to not try to match ondebug_assertions
Steps
1 - having .cargo/config.toml, this is based
cargo generate --git https://github.com/rust-embedded/cortex-m-quickstar
following the embedded book. I was trying to have different runners2 - cargo run
3 - cargo run --release
4 - There's a missing
-S
which is the difference.Possible Solution(s)
add runner to profile flags
Notes
No response
Version
The text was updated successfully, but these errors were encountered: