CMake Presets json file

[sillydan1]

This PR adds a CMakePresets.json with the Release preset , which makes it much easier to get started on development, as code-editors such as VSCode, CLion and neovim support generating compile_commands.json databases using these presets. It does require a fairly recent cmake version though.

I only added one preset, Release for now and I didn't dare touch the CI stuff, but perhaps this could simplify the CI chain.

I also found that the requirements.txt file in tools/mcuboot didn't mention the adafruit-nrfutil dependency, so I added that to the build instructions.

[github-actions]

Build size and comparison to main:

Section	Size	Difference
text	379128B	0B
data	948B	0B
bss	22536B	0B

Run in InfiniEmu

[mark9064]

Looks like a nice improvement overall :) Thanks for sending it in

I'm not sure about storing the toolchain inside the tree. Maybe environment variables like with the VSCode instructions would be more flexible? What are your thoughts, I do agree that having to configure env vars can be a bit annoying

[sillydan1]

Looks like a nice improvement overall :) Thanks for sending it in

I'm not sure about storing the toolchain inside the tree. Maybe environment variables like with the VSCode instructions would be more flexible? What are your thoughts, I do agree that having to configure env vars can be a bit annoying

Thanks! 😁 Hmm... I see your point that using raw environment variables is very flexible, I just found it a bit annoying to use though - which is why I added the cmake presets file... These changes will technically not prevent users from manually setting the environment variables and calling cmake without the --preset option, but then that means we need to support multiple workflows. Sadly, there's no way to "use the environment variable if defined, otherwise, use the ${fileDir}/sdk-toolchain value(s)"... At least I haven't been able to figure it out without needing to compromise on flexibility...

To me, ideally, the buildsteps should just be:

• Clone the project (with submodules)
• cmake --preset Release
• cmake --build build/Release

Where the CMakeLists.txt would download the SDK and toolchain for you at configure-time. I would love to try to get that done but it would require touching the CI and it would be a fairly big change to the now normal work flow, so I'm not sure if it would be too disruptive. Perhaps adding the presets just adds confusion and we should just close this PR?