Hi,
I am using nRF Connect SDK v3.3.0 with VS Code and nRF Connect for VS Code, targeting an nRF54L15.
I am currently trying to understand how an existing application works by starting from the official samples and progressively reconstructing the application myself.
I have noticed that many of the functionalities used by a sample are not implemented directly in the application's src/ directory. Instead, they are enabled through prj.conf / Kconfig, while the corresponding source files are located elsewhere within Zephyr or the nRF Connect SDK.
These source files are therefore part of the build, but are not physically located within the application's source tree.
I have already added the NCS directory to my VS Code workspace, which allows me to manually browse the SDK sources. I can also use features such as Go to Definition in some cases.
However, I would like to know whether there is a recommended way to obtain a convenient project view showing the source files actually included in the current build, including source files originating from Zephyr and the nRF Connect SDK.
Ideally, I would like these files to be presented in a way that makes it easy to navigate the application and understand which components and source files are being included as a result of the selected Kconfig configuration.
Is there a recommended way to achieve this using nRF Connect for VS Code, or any other functionality provided by development environment?
My intention is not to copy SDK source files into my application. I would like to keep the SDK unchanged and simply have a way to inspect and navigate the actual source files and dependencies involved in the build.
What workflow would you recommend for this purpose?
Thank you.
