Closed noppej closed 5 years ago
Yes, this was done intentionally to enable multiple code contributors. This concept allows us to share workspace without redefining target-specific paths on each fetch/update from other contributor.
If svd or cfg files are changed (which is unlikely, but possible), I would:
Perfect. I can live with that explanation. Would you like some help updating the docs?
PS. Thanks again for your work here. Being able to develop in VSCode is such a pleasure after being stuck with Eclipse based IDE's for STM for so long.
Would you like some help updating the docs?
Of course, If you find anything unclear, or have a better idea, go ahead and contribute! Once you create a pull request, I will just quickly check if everything is OK, and than merge. You are very welcome to do so :)
Thanks :) I am also a fan of VS Code and I use it on all projects now!
Thanks ... will do :)
Hi, I notice you now copy .SVD and board .cfg files to the .vscode folder. Is there a specific reason for that? I used the previous versions of your scripts (before you copy these files) very successfully, and found it cleaner to reference these files in their proper location.
If the .cfg file is updated, which one do we need to update, and will the update.py file re-copy the updated file?