Closed Barbacamanitu closed 1 year ago
Maybe a silly question - but this is what I often get when I'm not compiling with the correct target. Are you using the correct one?
I have my rusttoolchain.toml still from the last time it compiled. I have my .cargo folder with the config.toml set up correctly. Same as before. Is there something else I might be missing?
This exact project with this exact setup used to compile. I can't even compile the example project for my chip, the stm32f3. It does smell like a tool chain/target problem.
the error is definitely incorrect target. you need to either pass --target
to Cargo, or set it in .cargo/config.toml
.
I had to change my workspace level resolver to resolver = "2". If I moved my embassy related code out of my workspace, it compiled. I must have combined projects into a workspace at some point and forgotten.
They really should fix the fact that individual projects can have edition or resolver set to a specific value, but its ignored when those projects are in a workspace. I'm developing a local crate alongside my embedded firmware, and I need to be able to move between them and debug, so they're in the same workspace.
I haven't touched my code in a couple of weeks. I was about to make some changes to incorporate a new crate I wrote, and I thought I'd start by just running my old code. However, my unchanged code won't compile. I'm getting errors about inline asm not being able to find some functions.
The errors:
I was using a cloned embassy repository and specifying my embassy dependency using the local path. What could have changed to cause this issue?