Artur Sinila

Maybe `avr-specs` will be better?

@gnprice @jayvdb

@weihanglo what about integrating https://lib.rs/cargo-update into `cargo` itself?

Hello. As far as I understood, you are maintainer of this project. I think this issue is related to https://github.com/avr-rust/rust/issues/164. Do you have any ideas how to fix it?

I've ran into the same issue, unfortunately. Trying to make my university project in Rust. The deadline approaches rapidly, so most likely I'll just pick C.

@jonahbron Thank you for help, but I've figured out it myself short after my previous comment. Now I'm stuck with interrupts.

https://doc.rust-lang.org/cargo/commands/cargo-clean.html I guess `cargo clean --release` or `--profile dev` is exactly what you need.

> First, that would require substantial application refactoring and make business logic less clear. Second, on OSX about 30% of the compile time is in the linker and on Linux...

@LukeMauldin on GNU/Linux: 1. Install `lld` via your package manager 2. Write this into `$CARGO_HOME/config.toml`: ```toml [build] rustflags = [ "-C", "link-arg=-fuse-ld=lld", ] ``` or try `mold` instead of `lld`,...

@LukeMauldin `-fuse-ld=` option doesn't accept the path to linker binary, try this instead: ```rust [build] rustflags = [ "-C", "link-arg=--ld-path=/opt/homebrew/opt/llvm/bin/ld.lld" ] ```