Hello, I wanted to test the VS Code extension but it failed for the following use case...
In our company, we are building our product-related SDK that uses nRF Connect SDK "as a child". This is how a west workspace looks like:
. ├── application ├── bootloader ├── chester ├── mbedtls ├── modules ├── nrf ├── nrfxlib ├── test ├── tools └── zephyr
The directory application is the user's private Git project which "includes" our SDK (directory chester in our tree).
This is what we have in application/west.yml:
manifest:
version: "0.10"
remotes:
- name: hardwario-chester
url-base: [email protected]:chester
projects:
- name: sdk.git
remote: hardwario-chester
path: chester
import: true
self:
path: applicationThis is what we have in chester/west.yml:
manifest:
version: "0.10"
remotes:
- name: nrfconnect
url-base: https://github.com/nrfconnect
projects:
- name: sdk-nrf
remote: nrfconnect
revision: v1.7.0
path: nrf
import: true
Back to the problem: I am unable to open such a structure with the VS Code extension. I am able to open the application folder which includes prj.conf, but the extension asks for this:
The application version is different to the one in nrf/VERSION. Would you like to change manifest and update the west workspace?
I select No as this would break my workspace. Then I want to provide it with the build configuration, but our custom board defined in chester/boards/... is not available in the list.
Thank you. P.
