Update the rust-analyzer config and take packages out of workspace

This commit is contained in:
Jesse Braham 2022-05-31 10:02:55 -07:00
parent b382a019d4
commit 3669381234
2 changed files with 33 additions and 13 deletions

38
.vscode/settings.json vendored
View File

@ -1,7 +1,35 @@
{
"rust-analyzer.cargo.features": [
"esp32c3"
],
"editor.formatOnSave": true,
"rust-analyzer.checkOnSave.allTargets": false
}
"rust-analyzer.cargo.buildScripts.enable": true,
"rust-analyzer.cargo.noDefaultFeatures": true,
"rust-analyzer.checkOnSave.allTargets": false,
"rust-analyzer.imports.granularity.enforce": true,
"rust-analyzer.imports.granularity.group": "crate",
"rust-analyzer.procMacro.attributes.enable": false,
"rust-analyzer.procMacro.enable": true,
// -----------------------------------------------------------------------
// Since we have to handle multiple toolchains AND multiple targets, we
// we need to give Rust Analyzer some directions.
//
// Enable ONE target and linked project based on which chip you are
// developing for. This will propagate to the `esp-hal-common` crate too,
// as it is a dependency. Changing target/project requires reloading
// Rust Analyzer.
// "rust-analyzer.cargo.target": "xtensa-esp32-none-elf",
"rust-analyzer.cargo.target": "riscv32imc-unknown-none-elf",
// "rust-analyzer.cargo.target": "xtensa-esp32s2-none-elf",
// "rust-analyzer.cargo.target": "xtensa-esp32s3-none-elf",
"rust-analyzer.linkedProjects": [
// "esp32-hal/Cargo.toml",
"esp32c3-hal/Cargo.toml",
// "esp32s2-hal/Cargo.toml",
// "esp32s3-hal/Cargo.toml",
],
}

View File

@ -1,8 +0,0 @@
[workspace]
members = [
"esp-hal-common",
"esp32-hal",
"esp32c3-hal",
"esp32s2-hal",
"esp32s3-hal"
]