Closed LMESTM closed 1 year ago
The extension exposes a CMSIS Project Manager
output channel in VS Code that has the messages from the conversion. That's not ideal, since it isn't very obvious when there are errors. In the near future we plan to move from building CPRJ to building the csolution directly, so the conversion step won't be needed. At that point I expect this won't be a problem.
thanks, I was expecting this kind of logs to exist so that anwers my question :-)
In case the VScode extension settings are not properly set, or in case Integrated Terminal is set to git-bash instead of PowerShell, the cprj creation will fail, but it seems it will more or less silently fail
The errors would only pop-up during BUILD process, claiming that there is no cprj.
Are there any logs, or could there be logs, about the crpj creation process ? so that we can have a look to understand the origin of the issue when cprj files are missing.
Way to reproduce.
Select git-bash as default integrated terminal
Then select a new Active Solution and try to build. It will fail as there is no cprj, but no other error was raied before. That's not easy to understand what's wrong ...