VSCode Extension Intellisense, additional paths

[grant.r]

Hi,

I am using nRF Connect SDK v2.3.0. Using VSCode, nrf-connect is the configuration proider for c_cpp extension and intellisense.

I am trying to add some include paths (external test framework).

How can I add non-application paths to the c/cpp intellisense include path?

I have tried adding in a c_cpp_properties.json file as below, but the header includes still give a not found error

[Øyvind]

Hello, 

I'm not sure I understand your question. Are you trying to add Ceedling build system to the VS code extension? Could you please elaborate more on what you are trying to achieve?

Thank you.

Kind regards,
Øyvind

[grant.r]

I am just trying to get autocomplete working in my non-zephyr test files. Usually the C/C++ extension handles the intellisense fine, based on c_cpp_properties file.

With a non-ncs project, I normally just add the paths to the c_cpp_properties file, and intellisense picks the files up.

With the nrf connect extension it doesn't seem to honor the additions in this file.

I just want to add arbitrary folders/source files to intellisense, but remain using nrf-connect extension

[Øyvind]

Thanks for providing this information. Our VS Code team informs me that the extension pulls the include paths in from the compile_commands.json file generated by the build system. We had a bug related to this that was fixed in Friday's release, perhaps updating the extension might fix it.

Kind regards,
Øyvind

[grant.r]

Thankyou for the reply - to confirm, is there anyway to add out-of-project paths to intellisense?
Is it possible to add things to the generated compile-commands?

[Øyvind]

Our VS Code team replies "Not without adding it to the CMake build"

[grant.r]

Can I please request that the team looks at the possibility of also using paths from the c_cpp extension

The "C_Cpp[.default].includePath" setting

Thankyou

[Øyvind]

Thanks for your request. Our team will look into this, and write:

It does make sense, because that seems to be the behaviour of the C/C++ extension. If that extension only uses values from a provider (our extension in this case) and ignores its own configuration, then we need to feed its own configuration via our provider.

No timeline on when this will be ready.