-
Notifications
You must be signed in to change notification settings - Fork 335
Description
OS
Windows
Operating System version
Windows 11
Visual Studio Code version
1.105.1
ESP-IDF version
6.0.1
Python version
3.12.6
Doctor command output
Description
When using the IDF V6.0.1, navigating the sdkconfig using the headers displayed on the left no longer works.
note in the image I have selected "settings" but the view to the right stays the same.
note some of the item (just a few) the navigation seems to work for example: Support ESP32 internal EMAC controller seems to work.

Note it seems to be project dependent, the hello_world example works fine the:
examples -> protocols -> http_server -> restful_server sdk config navigation does not work
examples -> protocols -> mqtt -> tcp sdk config navigation does not work
examples -> get-started -> hellow_world sdk config navigation works
To reproduce:
open restful_server example from IDF V6.0.1
Run reconfigure task
Open sdk config (menu config) and try to navigate using the headers,
Maybe related to the esp_wifi component cmake warning?
CMake Warning at C:/Users/admin/esp/v6.1-dev/esp-idf/tools/cmake/component_validation.cmake:106 (message):
Private include directory
'C:/Users/admin/esp/v6.1-dev/esp-idf/components/esp_wifi/wifi_apps/roaming_app/include'
belongs to component esp_wifi but is being used by component
wpa_supplicant. It is recommended to define the component dependency for
wpa_supplicant on the component esp_wifi, i.e. 'idf_component_register(...
PRIV_REQUIRES esp_wifi)' in the CMakeLists.txt of wpa_supplicant, and
specify the included directory as idf_component_register(...
PRIV_INCLUDE_DIRS <dir relative to component>) in the CMakeLists.txt of
component esp_wifi.
Call Stack (most recent call first):
C:/Users/admin/esp/v6.1-dev/esp-idf/tools/cmake/component_validation.cmake:130 (__component_validation_check_include_dirs)
C:/Users/admin/esp/v6.1-dev/esp-idf/CMakeLists.txt:338 (__component_validation_run_checks)
I have also tested the pre-release version of the extension (it has the same issue)
The same example project from idf V5.5.1 does not have this issue.