Extra CMAKE arguments not saved in "Edit Build Configuration"

[Anthony Ambuehl]

I'm using Visual Studio with NCS 2.3.0.  

I want to pass an overlay to the mcuboot cmake. 

In the nRF Connect extension..Applications pane in the build configuratio I select "Edit Build Configuration"

In the "Edit Build Configurations"  under Extra CMake arguments I select "Add argument"

I enter -Dmcuboot_OVERLAY_CONFIG:STRING="D:/AAA/version_overlya.conf"

There is no option to save, I close the window.

I go back and again select "Edit Build Configuration"  

My extra CMake argument is now missing.  It was not saved.

[Sigurd Hellesvik]

Hi,

This looks like a bug in our VS Code extension.
Thank you for reporting this.

Is it important for you to add this overlay configuration in the VS Code GUI?
If not, I can suggest alternative methods for setting these.

Regards,
Sigurd Hellesvik

[Anthony Ambuehl]

Hi Sigurd, I have been testing this more and it seems like it will remember the extra arguments if the build/generate step is successful.

[Sigurd Hellesvik]

Anthony Ambuehl said:

Hi Sigurd, I have been testing this more and it seems like it will remember the extra arguments if the build/generate step is successful.

That is good to know, thanks!

Anthony Ambuehl said:

I need to find some way that I can apply a kconfig overlay for specific child images.  I would like to have multiple builds with different config overlays that add specific features.

Please do let me know if you have any recommendations.

From Multi-image builds:

Specifically:

    #     |-- <ACI_NAME>_<buildtype>.conf (J)     Fragment, used together with (B) and (D)

Also Important Build System Variables

Example project:

build_conf_feat_child_image.zip

Example project folder structure:

.
├── child_image
│   ├── mcuboot_log.conf
│   └── mcuboot_no_log.conf
├── CMakeLists.txt
├── prj_log.conf
├── prj_no_log.conf
├── README.md
├── sample.yaml
└── src
    └── main.c

Keep in mind that if you remove the default "prj.conf", it will increase the complexity of the build setup, so you should probably include instructions on how to set up a build for your project in a README or something. (I have received customer projects which I struggled to build due to them using build types)

Regards,
Sigurd Hellesvik