misterinterrupt
commented
1 year ago open the project vi the rriv-rust.workspace file, in vscode, rust analyzer will work in both cargo ws's at the same time.
cargo works on the cli inside of the board and src folders as cargo projects. Cargo won't do anything in the repo root folder since we want to have the .cargo/Config.toml with a x-compile target defined and rust-analyzer can't handle the nesting. I am happy with it, lmk what you think
16 use parallel cargo workspaces and vscode's multi-root workspaces instead of nested cargo workspaces