Open Rahix opened 2 months ago
The avr-hal-template
is updated to pin the dependency version. New projects generated from the template will no longer run into this problem. Unclear whether this is enough or whether we should do more...
avr-hal
itself also needs fixing for the examples.
For documentation, the dependency can be pinned using these lines in Cargo.toml
:
# The latest releases of `proc-macro2` do not support the rust toolchain that
# we use. Thus, we must fix this dependency to an older version where our
# toolchain is still supported. See https://github.com/Rahix/avr-hal/issues/537
[build-dependencies.proc-macro2]
version = "=1.0.79"
Examples in this repository now also have the dependency pin (#544).
So avr-device
will need to deal with this for its own CI, too. So maybe the solution is to simply pin proc-macro2
in avr-device-macros
so it will solve the problem for each and every downstream crate (See https://github.com/Rahix/avr-device/pull/156).
What does everyone else think about this? Are there any problems with doing this?
From #546: The CI of this project (avr-hal
) does not fail on this... Needs to be investigated.
Originally reported in #535.
Due to a change in
proc-macro2
versionv1.0.80
, the toolchain version we use is no longer supported (see https://github.com/dtolnay/proc-macro2/issues/451). To reproduce:which end with the following build error:
The solution to this issue comes in two parts:
proc-macro2
tov1.0.79
somewhere to ensure this won't hit us again. I am unsure where the right place for this is:avr-device
? Pulled in by everyone who might care about this, but feels like the wrong level for such a fix.avr-hal-template
? Gives users control over the fix, if it ever needs changing. Downside is that it does not reach existing users, only new ones...avr-hal/arduino-hal/atmega-hal
? Should allow reaching existing users more easily, but still not really the right level for the fix...