RE: CMakePresets.json, Build-Configs. Project Settings

cellular_iot — Fri, 23 May 2025 12:32:33 GMT

Thanks Edvin for sharing your workflow, will give it a try. That said - there definitely should be an easy way to fully save and restore a project with ALL settings and with relative paths - like all other IDEs do and did. Industry standard is that I can create multiple configs which combine baords, optimisations etc called target, all that stuff is saved and restored in the GUI, I can build one or all targets, flash and debug. I can easily version controll a project with all those settings, compare, roll-back changes etc. This seems to be missing or gone in nRF connect VScode in 2025.

RE: CMakePresets.json, Build-Configs. Project Settings

Edvin — Fri, 23 May 2025 12:15:20 GMT

Hello,

In general, I try to avoid storing things in the build folder, and I regularly delete all my build folders (when testing a lot of customer samples, the amount of build folders grows quite fast, and also the disk usage on my computer).

I must admit that I don't typically use the GUI tools, such as nRF Kconfig GUI or Menuconfig. I assume you are using the nRF Kconfig GUI, since you mention things being stored in the build folder:

However, if you instead select "Save to File", and specify to save it to prj.conf in the popup, then these changes will be stored in the prj.conf file, outside your build folder. Hence, if you just zip and transfer your application folder to a colleague (without a build folder), they should be able to just create their own build configuration, where all they specify is what NCS version they are using, and what board they are building for, and they should be able to build and flash, and have it behave the same way as it did on your computer.

Best regards,

Edvin