NRF Connect for VS Code doesn't save configuration changes

[Jeffrey Haynes]

I have been attempting to add a -Dmcuboot_OVERLAY_CONFIG item to the "Extra CMake arguments" section of the Build Configuration page.  When I do, the build successfully completes and the Build Configuration page closes.  Next time I open the build page, the CMake argument is missing.  I also can't figure out where the extension is meant to be saving this stuff.  Would be nice if there was a .json file or something to look at to see what's going on.

I should probably also note that upon creating a new project there are no CMake arguments.  After my item gets deleted, any arguments I've added get removed and instead a BOARD_ROOT item is added.

[Priyanka]

Hi Peter,

Peter Maxwell Warasila said:

However, this is still not taken into account either when editing the build configuration nor when performing a pristine build in the actions menu. T

Do you mean that when you edit something else or even when you d a pristine build, the extra CMake args are not being taken into account?

I have inquired internally and will get back to you soon.

-Priyanka

[Priyanka]

Hi Peter,

This could happen because you forget to click on the OK button when adding the extra argument. Without that OK it is not completed.

Please confirm by the build logs or by the hovering over the build that the argument is in fact used by CMake. For this to update the user must wait until the build is completed.

-Priyanka

[Peter Maxwell Warasila]

I have ensure that I clicked on the OK button. Just in case it makes a difference, I am using this format when adding the additional CMake argument: 
-Dmcuboot_OVERLAY_CONFIG:STRING="path/to/file"

As you can see, it is not being picked up the build hover tool tip. It is, however, appearing in my CMakeCache.txt file, along with another KConfig overlay which enables the partition manager:

//Extra config fragments for mcuboot child image
mcuboot_OVERLAY_CONFIG:STRING=path/to/file;C:/Users/Peter/ncs/v2.1.2/nrf/subsys/partition_manager/partition_manager_enabled.conf

Perhaps this has something to do with this particular case with the mcuboot overlay?

[Priyanka]

It does look strange as I was able to get the args added. I tried 

-Dmcuboot_OVERLAY_CONFIG:STRING="path/to/file" on the hello_world sample and it works. Which sample are you trying? Could you see if this works on other samples too?

-Priyanka

[Curiosus]

I have experienced exactly the same behavior, the only way I got this to work was to save the build configuration as a preset deleting the version of the build that did not save my flags or custom data and the creating a new build loading these presets. 

Priyanka  Could you please suggest a fix for this or is this an issue with the extension ? 

I can replicate it on any sample loaded.