Setting Zephyr directory in VS Code

Question

I've setup my development environment using the 'application' structure. https://docs.nordicsemi.com/bundle/ncs-latest/page/zephyr/develop/application/index.html#zephyr_workspace_application 
 I have all of the zephyr and nrf directories under the external directory. 
 I cannot get VSCode to use the 'external' directory. It always uses c:
cs\v2.6.1. 
 
 My .west/config looks like this: 
 [manifest] path = customername_folder file = west.yml 
 [zephyr] base = external/zephyr 
 
 and I've tried this: 
 [manifest] path = ..\..\_DSGit\customername\Code\external
rf file = west.yml 
 [zephyr] base = external/zephyr 
 Can you give me some idea what I'm missing? 
 During a west update, I can get something like this: 
 
 [17:44:05] ENOENT: no such file or directory, open 'c:\_DSGit\customername\Code\external\.west\config' (c:\_DSGit\customername\Code\external) 
 
 I updated to the latest plugin, which seems to provide extra flexibility on this, but no luck.

GabrielDS · Accepted Answer

The ultimate resolution had to do with the way we keep our repos. .west needs to be in the top of the repo. Then we had config like this: 
 
 [manifest] 
 path = Code /app 
 file = west.yml 
 
 [zephyr] 
 base = external / zephyr 
 
 This let us keep our Code/app structure lower in our repo tree and keep external (all the west repo pulls) in our top (and use .gitingore to ignore it). 
 
 We still have a west.yml in our 'app' folder. It keeps this nice. Most importantly, NCS can find the sdk and allow it to be selected. 
 
 west.yml for reference:

manifest : 
 self : 
 west-commands : scripts/west-commands.yml 
 path : app 
 
 remotes : 
 - name : ncs 
 url-base : https://github.com/nrfconnect 
 
 projects : 
 - name : nrf 
 remote : ncs 
 repo-path : sdk-nrf 
 revision : v2.6.1 
 import : true 
 import : 
 path-prefix : external 
 clone-depth : 1

Setting Zephyr directory in VS Code

Top Replies