fix support for multiple sdkconfig files

[brianignacio5]

Description

Fix support of multiple sdkconfig when using Project Configuration and multiple profiles.

Fixes #1202
Fixes #1265
Fixes #1283
Fixes #1299

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)

Steps to test this pull request

Using a project with multiple configurations like https://github.com/espressif/esp-idf/tree/master/examples/build_system/cmake/multi_config run the ESP-IDF: Open Project Configuration and configure 2 profiles with different SDK Configuration Editor, resulting in a esp_idf_project_configuration.json like this:

{
  "gen1": {
    "build": {
      "compileArgs": [],
      "ninjaArgs": [],
      "buildDirectoryPath": "${workspaceFolder}/build_gen1",
      "sdkconfigDefaults": [
        "sdkconfig.prod_common",
        "sdkconfig.prod1"
      ],
      "sdkconfigFilePath": "${workspaceFolder}/sdkconfig1"
    },
    "env": {},
    "flashBaudRate": "",
    "idfTarget": "",
    "monitorBaudRate": "",
    "openOCD": {
      "debugLevel": 0,
      "configs": [],
      "args": []
    },
    "tasks": {
      "preBuild": "",
      "preFlash": "",
      "postBuild": "",
      "postFlash": ""
    }
  },
  "gen2": {
    "build": {
      "compileArgs": [],
      "ninjaArgs": [],
      "buildDirectoryPath": "${workspaceFolder}/build_gen2",
      "sdkconfigDefaults": [
        "sdkconfig.prod_common",
        "sdkconfig.prod2"
      ],
      "sdkconfigFilePath": "${workspaceFolder}/sdkconfig2"
    },
    "env": {},
    "flashBaudRate": "",
    "idfTarget": "",
    "monitorBaudRate": "",
    "openOCD": {
      "debugLevel": 0,
      "configs": [],
      "args": []
    },
    "tasks": {
      "preBuild": "",
      "preFlash": "",
      "postBuild": "",
      "postFlash": ""
    }
  }
}

Note: If using the former ESP-IDF multi config example, remember to remove from root CMakeLists.txt the line:

set(SDKCONFIG "${CMAKE_BINARY_DIR}/sdkconfig")

1. Click on "SDK Configuration Editor" using profile 1. SDK Configuration changes should be saved in ${workspaceFolder}/sdkconfig1 and c_cpp_properties.json should have compileCommands set to the build path of profile 1.

2. Click on "SDK Configuration Editor" using profile 2. SDK Configuration changes should be saved in ${workspaceFolder}/sdkconfig2 and c_cpp_properties.json should have compileCommands set to the build path of profile 2.

3. Observe results.

• Expected behaviour:

• Expected output:

How has this been tested?

Manual Testing

Test Configuration:

• ESP-IDF Version: 5.2
• OS (Windows,Linux and macOS): macOS

Checklist

• PR Self Reviewed
• Applied Code formatting
• Added Documentation
• Added Unit Test
• Verified on all platforms - Windows,Linux and macOS

[github-actions]

Download the artifacts for this pull request:

• esp-idf-extension.vsix.zip
  Espressif docs preview

[executer-uno]

Hello.
Thanks for fast fix. But can you please check #1265 - as for me, there is one issue left.

[radurentea]

LGTM

[brianignacio5]

Hi @executer-uno , please take a look at latest changes. It should kill the current sdkconfig editor process as described in your GitHub issue.

[executer-uno]

Thanks. That one tested and no issues left, as for me.

[github-actions]

Pull request has been marked as stale since there are no activities, and this will be closed in 5 days if there are no further activities

[github-actions]

Pull request has been marked as stale since there are no activities, and this will be closed in 5 days if there are no further activities

[Fabricio-ESP]

Tested on Windows 11 and Ubuntu 24.04 environment. The sdkconfig files define in the project configuration abe being updated properly when running menuconfig, instead of the file in the build folder.
The target configuration is now being read from the sdkconfig file, for the scenario where the file does not exist (not created by the user, and not being generated yet) the target device is not updated in the status bar. As an improvement we could set the target as ESP32 (which is the default target) when a target is not found in the sdkconfig file, to avoid any confusion for the user. But understood that this feature is used mainly by advanced users, which are familiar with the workflow to set the device target.