What is the source for menuconfig/guiconfig/nRF Kconfig GUI?

[PeterRasmussen]

Hey

I'm trying to figure out what is the intetned way of using the tools for configuring a project.

We have the following config files in the following structure:

.
├── boards
│   ├── arm
│   │   ├── app_nrf5340
│   │   │   ├── Kconfig
│   │   │   ├── Kconfig.board
│   │   │   ├── Kconfig.defconfig
│   │   │   ├── app_nrf5340_cpuapp_defconfig
│   │   │   ├── app_nrf5340_cpunet_defconfig
│   │   │   ├── app_nrf5340_partition_conf.dts
│   │   │   └── app_nrf5340_shared_sram_planning_conf.dts
│   │   └── nrf5340dk_nrf5340_cpuapp.overlay
│   └── debug_tools.conf
├── Kconfig
├── Kconfig.sysbuild
├── netcore
│   ├── prj.conf
├── prj.conf
├── sysbuild
│   └── mcuboot.conf
├── sysbuild.conf
├── west.yml

Depending on what i choose in the build configuration: 

Different things happen when i open any of the config tools. 

Can anyone tell me what is the intetned behavior, and even more is it correct that on not supposed to use the save minimal config? 

When i save minimal config it seems like i'm getting a  merge of all the different config files. 

[Menon]

Hello,

As far as I know, enabling the "save minimal configuration" option should generate a minimal configuration file that includes only the differences from the default settings. Let's discuss the steps to achieve this or to reproduce the issue. I recommend starting with a clean build and ensuring that prj.conf and other .conf files contain only the settings specific to their purpose. Then, use the menuconfig or a similar tool. Open menuconfig and make your changes. After making the changes, save the minimal configuration. Now, check the defconfig file inside the build folder to see if it reflects the configuration you selected in menuconfig or guiconfig.

Please let me know if this is not the case or if there is any confusion.

Kind Regards,

Abhijith