You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
INFO crank > build command: RUSTFLAGS="-Ctarget-cpu=cortex-m7 -Clink-args=--emit-relocs -Crelocation-model=pic -Cpanic=abort" "cargo" "+nightly" "build" "--lib" "--target" "thumbv7em-none-eabihf" "-Zbuild-std=core,alloc" "-Zbuild-std-features=panic_immediate_abort"
error: no such command: `+nightly`
Cargo does not handle `+toolchain` directives.
Did you mean to invoke `cargo` through `rustup` instead?
Error: cargo failed with error ExitStatus(unix_wait_status(25856))
I've been using a local copy of crank that removes +nightly and everything seems to work fine.
What's the motivation for adding +nightly when the --device flag is provided?
The text was updated successfully, but these errors were encountered:
When providing the
--device
flag,+nightly
is added tocargo build
:crank/src/main.rs
Lines 611 to 615 in f46cda4
and I run into the following error:
I've been using a local copy of
crank
that removes+nightly
and everything seems to work fine.What's the motivation for adding
+nightly
when the--device
flag is provided?The text was updated successfully, but these errors were encountered: