NRF Connect Extension: Build Configuration CACHED CONF and extra Cmake args

RE: NRF Connect Extension: Build Configuration CACHED CONF and extra Cmake args

JyriLehtinen — Thu, 30 May 2024 08:51:45 GMT

I think it's okay, though I didn't find a detailed description on how the CMake caching works.
At least while using prj.conf (and possible other Kconfig fragments) it seems that the actual build process works nicely and is consistent as well.

RE: NRF Connect Extension: Build Configuration CACHED CONF and extra Cmake args

Einar Thorsrud — Wed, 29 May 2024 14:23:42 GMT

Hi,

Thank you for the detailed description. I see the same now. This will be fixed in the next release of the extension and is also fixed in the latest pre-release version (so you can switch to that if you want, but note that the pre-release version may have other issues).

RE: NRF Connect Extension: Build Configuration CACHED CONF and extra Cmake args

JyriLehtinen — Wed, 29 May 2024 12:51:15 GMT

I did a little testing, and in the process the nRF Connect extension was reloaded and updated. It seems the prj.conf is at least refreshed if there's changes in the file, could be that my problem was elsewhere as I can't reproduce it.
Anyhow, the extensions still changes the "Configuration" to the "Use CACHED_CONF_FILE argument", though it might not be a problem in this case as the argument value points to the project prj.conf.

Visual Studio Code
Version: 1.89.1
Commit:
dc96b837cf6bb4af9cd736aa3af08cf8279f7685
Date: 2024-05-07T05:16:23.416Z (3 wks ago)
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Linux x64 5.15.0-89-generic (Ubuntu 22.04)

nRF Connect for VS Code
V2024.3.25
SDK & Toolchain 2.6.1

Steps to reproduce

Create a new application (copy a sample: serial_lte_modem)
Add new build configuration
1. nrf9161dk_nrf9161_ns
2. Set Configuration to prj.conf
3. Press Build Configuration
The project should build successfully.
Editing the Build Configuration shows the Configuration dropdown now has a preset of "Use CACHED_CONF_FILE argument".
1. The value of the "Extra CMake arguments now include:

-DBOARD_ROOT="/home/jyri/nrf_ws/serial_lte_modem"
-Dmcuboot_OVERLAY_CONFIG="/home/jyri/ncs/v2.6.1/nrf/modules/mcuboot/tfm.conf;/home/jyri/ncs/v2.6.1/nrf/modules/mcuboot/fih_low_enable.conf;/home/jyri/ncs/v2.6.1/nrf/subsys/partition_manager/partition_manager_enabled.conf;/home/jyri/nrf_ws/serial_lte_modem/child_image/mcuboot.conf"
-DCACHED_CONF_FILE="/home/jyri/nrf_ws/serial_lte_modem/prj.conf"

It seems this is working as intended, it's just that in the past (like a year or more back) I don't recall the extension adding those arguments, at least they weren't displayed while editing the build configuration

RE: NRF Connect Extension: Build Configuration CACHED CONF and extra Cmake args

Einar Thorsrud — Tue, 28 May 2024 14:04:14 GMT

Hi,

I have not been able to reproduce this. Can you share wich nRF Connect SDK and which versino of the nRF Connect for VS Code plution you are using, along with exact steps on how to reproduce?

RE: NRF Connect Extension: Build Configuration CACHED CONF and extra Cmake args

JyriLehtinen — Tue, 28 May 2024 07:14:23 GMT

It seems every time pristine build is called from the extension, it adds those arguments and changes the configuration dropdown to cached. This means we have edit the build configuration and remove the extra arguments and set the configuration file back to prj.conf every time they need to be updated.

Happens on Linux (Ubuntu 22.04) as well as Win 11.

RE: NRF Connect Extension: Build Configuration CACHED CONF and extra Cmake args

Einar Thorsrud — Thu, 11 Apr 2024 12:40:21 GMT

Hi,

You mean the Ektra Cmake arguments in your screenshot? If you hower over the argument you shold see a pencil icon and a cross icon to the right, an di fyou click the cross, you remove it. If this is not it, perhaps you can elaborate a bit more what the problem is?