This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Pristine Build ignores CMake presets in nRF Connect for VS Code.

Hi.

I'd like to make use of CMake's presets, but it seems like nRF Connect for VS Code is forgetting about my presets when I hit "pristine build". 

I've created an application and added a build configuration.  In the "Extra CMake arguments", I've passed the argument "--preset debug", which corresponds to a preset in my CMakeUserPresets.json file.  It seems as though the build works the first time, and I can see the --preset debug argument in the west command.  If I then hit "pristine build", the new generated command doesn't include the --preset argument, and seems to be pulling some arguments, such as -DCONF_FILE from the CMake cache, which is strange.  The net result is that I can never use pristine build if I also define part of my build environment in my presets, as these definitions will no longer be present and the build will fail.  If I want to build again, I have to delete this build configuration and make a new one, passing the preset to it again.

I'm new to both CMake presets and nRF Connect for VS Code.  Is this the expected behaviour?  How can I bring in my presets again when I build?

Parents Reply Children
Related