-
Notifications
You must be signed in to change notification settings - Fork 126
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
IDF_TARGET not set #345
Comments
What do you expect? You are declaring a proc-macro library. These run on the host. |
[[bin]]
name = "billiards_esp32"
harness = false # do not use the built in cargo test harness -> resolve rust-analyzer errors
[lib]
proc-macro = true but, I also have a bin crate |
It does not work like that. You are chasing rust restrictions, misinterpreting the error and then opening as bug here. What
It is rustc and cargo themselves who are not picking your esp32 target, not |
[lib]
proc-macro = true The target is specified in. cargo/config |
@ivmarkov |
OK I give it one last try: what you are trying to do (mixing a proc-macro crate together in another, non-proc-macro crate) is just NOT possible in Rust. This is not a problem of Try to do what you are trying to do with any other embedded framework - be it The only solution is to have your proc-macros in a separate, dedicated proc-macro crate. As everybody else does. Google the internet for that. |
Thank you very much for your patient answer, I have now placed it in a separate crate |
After adding this parameter to Cargo.toml, the build failed
build log:
The text was updated successfully, but these errors were encountered: