How can I tell the nRF Connect VS Code extension where the nRF Connect SDK is located?

[lagrangepoint1]

Our team is transitioning to the nRF Connect SDK after extensive experience with older nRF SDKs and custom build systems (based on cmake + west + python) integrated with VS Code.

We plan to use the CLI primarily, but would like to leverage the nRF Connect VS Code extension for debugging.

Currently, the build configuration for the extension always points to `~/ncs/vX.Y.Z` and does not allow us to specify a custom SDK location. This setup does not work for our workflow, as our repository uses a west manifest to pull the SDK into a specific directory.

Is there a way to configure the nRF Connect VS Code extension to use an SDK located at a custom path, as defined by our west manifest?

[Vidar Berg]

Hello,

I think the easiest way to do this is to navigate to your West workspace in the terminal, then type "code . " to open VS Code in that directory. The extension should then automatically recognize the new workspace and allow you to select the SDK specified in your manifest from the build configuration.

Documentation for our Vs code extension for reference: https://docs.nordicsemi.com/bundle/nrf-connect-vscode/page/guides/workspaces.html 

Best regards,

Vidar