I would recommend to add compilerPath to xtensa's gcc for the C/C++ extension to pick up basic c libraries and use the compile_commands.json if you are able to build successfully for more accuracy.

Well there are several things here as mentioned in the Problems tab: Environment variables are referenced different in Windows than Linux. For a cross platform approach, try to use ${env:<var>} for example ${env:IDF_PATH} . The compiler path is different in Windows. Check your ESP-IDF setup location...

You should be able to work with any project with the ESP-IDF vscode extension if the folder structure follow this structure: - myProject/ - CMakeLists.txt - sdkconfig - components/ - component1/ - CMakeLists.txt - Kconfig - src1.c - component2/ - CMakeLists.txt - Kconfig - src1.c - include/ - compon...

Hey Dirk sorry for late reply. Could you please try this [vsix installer](https://nightly.link/espressif/vscode-esp-idf-extension/actions/artifacts/106830649.zip) we made several fixes to the setup wizard and hopefully your issue is already fixed. Here is how to install an extension from a vsix file .

Check if your project directory has a `.vscode/settings.json` file with configuration settings such as `idf.espIdfPath` overriding the user level settings. Make sure to: 1) Choose Select where to save configuration settings command and choose the workspace folder to save the settings. 2) Or `.vscode...

In the ESP-IDF extension we have a template tasks.json which is included when you create a project with extension commands. template tasks.json where for example the build task has a problem matcher defined to get errors shown at the Problems tab. This task is using extension settings to resolve bin...

How are you building ?

Are you using a custom task in tasks.json ? You can customize the task output so it can parse those source files location so you can jump from the output.

Are you using an extension, which one ?

Can you share the log file ?

https://github.com/espressif/vscode-esp ... leshooting

If it is asking to choose this it is probably because visual studio code doesn't find a launch.json for the current project.

Is there a .vscode/launch.json ?

Are you opening one ESP-IDF project or several projects at the same time ?

Based on your logs: CMake Error at C:/Users/XXXX/esp/esp-idf/tools/cmake/component.cmake:224 (message):\n CMake Error at\n C:/Users/XXXX/esp/esp-idf/tools/cmake/scripts/component_get_requirements.cmake:97\n (include):\n\n include called with wrong number of arguments. include() only takes one\n file...