ESP-IDF c_cpp_properties VScode configuration file

c_cpp_properties .json

{
    "configurations": [
        {
            "name": "ESP-IDF",
            "cStandard": "c11",
            "cppStandard": "c++17",
            "compileCommands": "${workspaceFolder}/build/compile_commands.json",
            "includePath": [
                "${workspaceFolder}/build/config",
                "${config:idf.espIdfPath}/components/**",
                "${config:idf.espIdfPathWin}/components/**",
                "${workspaceFolder}/**"
            ],
            "defines": [
                "_DEBUG",
                "UNICODE",
                "_UNICODE"
            ],
            "browse": {
                "path": [
                    "${workspaceFolder}/build/config",
                    "${config:idf.espIdfPath}/components",
                    "${config:idf.espIdfPathWin}/components",
                    "${workspaceFolder}"
                ],
                "limitSymbolsToIncludedHeaders": false
            },
            "compilerPath": "C:\\Users\\moise\\.espressif\\tools\\xtensa-esp32-elf\\esp-12.2.0_20230208\\xtensa-esp32-elf\\bin\\xtensa-esp32-elf-gcc.exe",
            "intelliSenseMode": "windows-gcc-x86"
        }
    ],
    "version": 4
}

This is a sugestion of how the file must be to allow the vscode find all the files, symbols and imports needed.
After setting the file like this, hit the build button, because some symbols will still be missing before the build, because they are created in the build process.

• The "${workspaceFolder}/build/config", resolves the missing settings that are already in the sdkconfig
• The "${config:idf.espIdfPath}/components/**" and "${config:idf.espIdfPathWin}/components/**" solves the problem that the VSCode says that cannot find any library from the ESP-IDF