After 86d407b("tools:scripts: Don't overwrite .vscode config if it already exists") the vscode configuration files (contents of the .vscode directory) are no longer overwritten on every make build. This may lead to confusion if the build was acciedentally done for a different platform than the one intended.
Such a situation may occur if the user runs "make build" (without the PLATFORM variable), resulting in generating the vscode configurations for the STM32 platform. From this point there is no way to change the target to another platform using the build system. Fix this by removing the .vscode directory on "make reset".
Pull Request Description
Please replace this with a detailed description and motivation of the changes.
You can tick the checkboxes below with an 'x' between square brackets or just check them after publishing the PR.
If this PR contains a breaking change, list dependent PRs and try to push all related PRs at the same time.
PR Type
[ ] Bug fix (change that fixes an issue)
[ ] New feature (change that adds new functionality)
[ ] Breaking change (has dependencies in other repos or will cause CI to fail)
After 86d407b("tools:scripts: Don't overwrite .vscode config if it already exists") the vscode configuration files (contents of the .vscode directory) are no longer overwritten on every make build. This may lead to confusion if the build was acciedentally done for a different platform than the one intended.
Such a situation may occur if the user runs "make build" (without the PLATFORM variable), resulting in generating the vscode configurations for the STM32 platform. From this point there is no way to change the target to another platform using the build system. Fix this by removing the .vscode directory on "make reset".
Pull Request Description
Please replace this with a detailed description and motivation of the changes. You can tick the checkboxes below with an 'x' between square brackets or just check them after publishing the PR. If this PR contains a breaking change, list dependent PRs and try to push all related PRs at the same time.
PR Type
PR Checklist