mcgordonite
commented
1 year ago Hi @jankap, thanks for reporting this issue.
There is indeed a bug with the extension in devcontainers. If you also have the extension installed on your local machine, VS Code will currently try to use that rather than installing the extension in the devcontainer. Since the workspace files aren't on your local machine, the extension fails to load your solution.
We'll release a fix for this soon, so VS Code will install the extension in your remote container.
In general, I'm missing configuration options like the path to the SW components, where to search for project files, where to find the FLEXLM server, and so on.
- What do you mean by the "path to the SW components" configuration here? Do you mean how to configure where the CMSIS packs are installed, or where the configuration files for software components are stored?
- We've recently added a "Solution" panel to the CMSIS view. This shows an outline of the solution. It's still very much a work in progress, but it already shows files from your solution's projects.
Type: Bug Report
Describe the bug
I'm running VSCode in a devcontainer basing on Ubuntu.
cbuildetc. is able to build my project properly. But the VSCode extension seems not to work. It only finds a csolution file, no contexts, no projects (the .cproject.yml exists) are shown:SW Components are empty, too:
But they are installed:
In general, I'm missing configuration options like the path to the SW components, where to search for project files, where to find the FLEXLM server, and so on.
Is the extension not yet ready to be used in remote container development?
Thanks :)
Screenshots
Additional context