build "hang" while installing GIT based platform/frameworks.

When building a project for the first time and the dependent platform(s) are not installed the console output will appear to “hang” with the following output:

> Executing task in folder ESP32CommandStation: .....\platformio.exe run --environment pcb_oled_sh1106 <

Processing pcb_oled_sh1106 (platform: https://github.com/platformio/platform-espressif32.git; board: esp32dev; framework: espidf, arduino)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

This project is using the GIT versions for arduino-esp32 and esp-idf via the following platformio.ini overrides:

[env]
# overrides to use GIT versions rather than PIO cached copies.
platform_packages =
  framework-arduinoespressif32 @ https://github.com/espressif/arduino-esp32.git
  framework-espidf @ https://github.com/espressif/esp-idf.git#release/v3.2

[ivankravets]

Thanks! A few good things:

1. New integration for ESP-IDF 4 will be based on the CMake generator. So, we will use CMake to get a list of build items and use the PlatformIO Build system for the rest tasks. We already did this for Zephyr RTOS. It means that you can anytime build the same project with idf.py or PlatformIO.
2. “menuconfig” - yes, there is a feature request and we will try to resolve it soon.
3. We currently support only stable software. However, if we will support CMake provided information, it should be possible to use dev-version of ESP-IDF too. It depends on ESP-IDF build process and that all steps are declared in CMake. Otherwise, we will not know how to build some targets which are no declared in CMake.

[atanisoft]

I believe the two plugins can work together but they may have conflicts in the .vscode directory for paths since IDF usually resides in /home/<user>/esp or similar path.

The plugin has three advantages over PIO currently:

1. Native CMake integration, same as running idf.py <target> which invokes CMake.
2. Graphical “menuconfig” within VSCode.
3. Easy switching of IDF versions (git checkout – <tag>) without needing to upgrade/downgrade the plugin to ensure the build works.

Since my project no longer has Arduino dependencies, it makes sense for me to use the lower level IDF approach.