• State Not Answered
  • Replies 15 replies
  • Subscribers 78 subscribers
  • Views 3294 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 296616
Options

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.

Parents
  • 0

    I think I see now.  Basically it's just setting up build directories and configuring everything. 

    So going back to a configuration and editing it is meaningless?  Why is it an option then?

  • 0 in reply to Jeffrey Haynes

    Hi Jefferey,

    Sorry for the delayed response. 

    Next time I open the build page, the CMake argument is missing. 

    Do you mean when you open this build page

    This is just an interactive page to build the project and once you have built it, all your requirements will be added to the project and opening this page again will not show the arguments you have set for the previous "build".

    Also, when you add the "Extra CMake arguments", you are making a change to the input file and it is recommended to "Pristine Build" in such cases.

    -Priyanka

  • 0 in reply to 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
  • 0 in reply to Priyanka

    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?

  • 0 in reply to Peter Maxwell Warasila

    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

  • 0 in reply to Priyanka

    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. 

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

    I can replicate it on any sample loaded. 

  • 0 in reply to Curiosus

    Hi,

    Have you tried the steps or suggestions mentioned earlier?

    Priyanka said:

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

    Priyanka said:
    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.

    And is it being picked up by the build hover?

    -Priyanka

Reply
  • 0 in reply to Curiosus

    Hi,

    Have you tried the steps or suggestions mentioned earlier?

    Priyanka said:

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

    Priyanka said:
    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.

    And is it being picked up by the build hover?

    -Priyanka

Children
Related
Terms of service