Kconfig defines not showing in ifdef, ifdef greyed out

RE: Kconfig defines not showing in ifdef, ifdef greyed out

Edvin — Thu, 13 Apr 2023 07:27:55 GMT

Sorry for the late reply. I was out of office last week due to public holidays here in Norway.

Ifdefs in itself works, the issue is for the IDE to understand what configurations that are currently selected. Especially if you have multiple projects open at once. I will forward your ticket to our nRF Connect for VS Code team, but I think it is a mix of our tool, and the external tools that they use that causes the highlighting to not always be correct. If you are in doubt whether a config is set or not, you should check the build folder:

build\zephyr\include\generated\autoconf.h, to see what your build actually uses. Remember that it is not that easy for the IDE to actually predict what all the definitions will be without actually compiling the application, which it obviously doesn't do all the time when you are editing.

So as I mentioned in my initial reply, the highlighting is guiding, and nice to have, but you should be aware that it is not always correct (that goes both ways).

Best regards,

Edvin

RE: Kconfig defines not showing in ifdef, ifdef greyed out

Martijn-Revival — Mon, 03 Apr 2023 18:42:12 GMT

Thanks for the answer. Too bad that full support for ifdefs is not available. Is that something which might be available in the future?

RE: Kconfig defines not showing in ifdef, ifdef greyed out

Edvin — Thu, 30 Mar 2023 13:57:21 GMT

Hello,

The highlighting in VS Code should be for guidance only. It doesn't always understand what's included or not. If it doesn't work in your case, you can disable it (many of my colleagues have, while I like to use it, with an asterisk, knowing what it shows is not always correct).

Best regards,

Edvin