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
Right now we essentially have env AVR_CPU_FREQUENCY_HZ=16000000 cargo +nightly build -Z build-std=core --target avr-atmega328p.json --release, which is fairly long.
Maybe it is better that users have to type in the target and build-std flags so they become aware of their necessity, but otherwise they could be omitted with the use of .cargo/config.toml. Perhaps a note about them in the README would be enough?
At which point the command is simply cargo +nightly build --release (once the LLVM error is resolved and the user has a new enough cargo). We don't even need +nightly if ./rust-toolchain is added.
The text was updated successfully, but these errors were encountered:
Right now we essentially have
env AVR_CPU_FREQUENCY_HZ=16000000 cargo +nightly build -Z build-std=core --target avr-atmega328p.json --release
, which is fairly long.Maybe it is better that users have to type in the target and build-std flags so they become aware of their necessity, but otherwise they could be omitted with the use of
.cargo/config.toml
. Perhaps a note about them in the README would be enough?At which point the command is simply
cargo +nightly build --release
(once the LLVM error is resolved and the user has a new enough cargo). We don't even need +nightly if./rust-toolchain
is added.The text was updated successfully, but these errors were encountered: