-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can not build on nightly rust // Can't build any embassy example at all! #29
Comments
Already reported by others here embassy-rs/embassy#3078 and likely the issues is affecting embassy since nightly-2024-06-13 |
Thanks. A nightly rust-toolchain lock should be added before embassy's next crates.io release. |
And add the requested target. See ch32-rs/ch32-hal#29 and embassy-rs/embassy#3078
* fix(build): lock nightly toolchain See-also: #29 * fix(ci): use nightly-2024-06-12
Added |
Another # Cargo.toml
[patch.crates-io]
embassy-executor-macros = { git = 'https://github.com/embassy-rs/embassy' } |
A third way to work around:
I prefer this, due to the problem likely being temporary in nature. p.s. @jsprog my experience is that Embassy can be used with |
The problem here is that qingke_rt requires nightly because it uses naked_function. This can be worked around by generating some assembly wrapper like thr stm32 stuff does. But it is currently not implemented |
@Codetector1374 Thank you for the suggestion. I'm currently on holiday, but I plan to implement this when I return. Of course, pull requests are always welcome. 😊 |
Close as fixed. |
I'm having a hard time trying to make at least one embassy example work. Unfortunately, I confirmed that none of the official examples worked, event with the newer cargo-generate template (ch32-hal-template). According to other issues and discussions in this repository, it appears that this problem is unlikely to be affecting every developer! probably proc-macro incompatibilities across nightly revisions!
The error messages bellow were received after trying to build
examples/ch32v003/src/bin/embassy_blinky.rs
withcargo build --release --bin embassy_blinky.rs
orcargo build --bin embassy_blinky.rs
and I confirmed that I'm receiving the same error messages with every other embassy example regardless of the target device.Build errors
More Details from Rust Analyzer
proc-macro panicked: failed to load macro: Failed to get file metadata for /home/developer/dev/ch32-hal/examples/ch32v003/target/debug/deps/libembassy_executor_macros-ca73f4ef56da3f51.so: No such file or directory (os error 2)rust-analyzer[macro-error](https://rust-analyzer.github.io/manual.html#macro-error)
The text was updated successfully, but these errors were encountered: