I have mixed feelings about Docker-based solutions like cross. On one hand when they work, that’s nice.
But when it doesn’t work out of the box (e.g. cross breaks Cargo workspaces), you’re left with nothing. Rust has no real documentation on how to do cross-compile without cross. All existing guides are like the “how to draw an Owl” meme: “add --target and then solve all other problems yourself.”
Totally agree. I’d also say that this is a sad state of affairs because rust is so obviously well suited for embedded systems. Its like a match made in heaven really. The way they set up the HAL is such a good plan. I would LOVE to be able to just cross compile easily without all the setup.
I have mixed feelings about Docker-based solutions like
cross. On one hand when they work, that’s nice.But when it doesn’t work out of the box (e.g.
crossbreaks Cargo workspaces), you’re left with nothing. Rust has no real documentation on how to do cross-compile withoutcross. All existing guides are like the “how to draw an Owl” meme: “add--targetand then solve all other problems yourself.”Totally agree. I’d also say that this is a sad state of affairs because rust is so obviously well suited for embedded systems. Its like a match made in heaven really. The way they set up the HAL is such a good plan. I would LOVE to be able to just cross compile easily without all the setup.
@kornel Rust does have documentation : https://github.com/japaric/rust-cross
Thank you!