Upgrading to NCS V2.2.0

RE: Upgrading to NCS V2.2.0

Susheel Nuguru — Thu, 15 Dec 2022 20:11:14 GMT

Seems like it. Greate find Mike. This will be useful info as it is easy to miss.

RE: Upgrading to NCS V2.2.0

Mike Austin (LPI) — Thu, 15 Dec 2022 01:41:16 GMT

Hi Susheel,

I just noticed this on the GitHub repo for sdk-nrf:

This is basically what I'm seeing, so I'm assuming its a zephyr thing that now requires <zephyr/...> to be added to all the zephyr based includes

Regards,

Mike

RE: Upgrading to NCS V2.2.0

Susheel Nuguru — Wed, 14 Dec 2022 19:58:31 GMT

Thanks for the project Mike, I will give it a try and let you know my observations on it.

RE: Upgrading to NCS V2.2.0

Mike Austin (LPI) — Wed, 14 Dec 2022 09:59:51 GMT

Hi Susheel,

Attached is a simple project that shows the behaviour I am referring to.devzone.nordicsemi.com/.../5504.littlefs_5F00_example.zip

When I build this under V2.0.0, it completes without errors. But if I try and build under V2.2.0, then I need to add "zephyr/" to most of the includes in order for them to get picked up correctly

Regards,

Mike

RE: Upgrading to NCS V2.2.0

Susheel Nuguru — Wed, 14 Dec 2022 06:19:38 GMT

Hi Mike,

The samples we have in our SDK have the includes added properly to the build structure and when building manually or using Visual Studio Code you find that all samples builds properly. But if you have structured your project differently or building it in a different way or pulled in some other dependencies into the project to add new features, then it is normal that we need to add those dependencies into the CMakeLists.txt file.

So, your changes in the CMakeLists.txt file should have been pulled by the KConfig inclusion of those modules you tried to pull in your proj.conf file. Can you attach your project here so that I can quickly check if you pulled in your new dependencies in the right way into the proj.conf?