ESP32 unable to build hell_world with "master" branch

Sysprogs forums Forums VisualGDB ESP32 unable to build hell_world with "master" branch

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #23942
    kevinn
    Participant

    Hi

    I imported the “hello_world” project in Visual Studio with VisualGDB and got this error when try to build it.

    Note: If I build it from mingw32 windows using “make” command it work fine.

    Look like the script is missing something?

    Traceback (most recent call last):
    File “C:\DevTools\VisualGDB\esp-idf\master\tools\ldgen\ldgen.py”, line 22, in <module>
    from fragments import FragmentFileModel
    File “C:\DevTools\VisualGDB\esp-idf\master\tools\ldgen\fragments.py”, line 20, in <module>
    from sdkconfig import SDKConfig
    File “C:\DevTools\VisualGDB\esp-idf\master\tools\ldgen\sdkconfig.py”, line 18, in <module>

    How do I troubleshoot it?

    Thanks

     

    —— Build started: Project: hello-world, Configuration: Debug VisualGDB ——
    VisualGDB: Run “C:\PROGRA~2\Sysprogs\VisualGDB/ninja.exe ” in directory “D:\Espressif\Projects\examples\get-started\hello_world/VisualGDB/Debug” on local computer
    [1/7] Generating esp32.common.ld
    FAILED: esp-idf/esp32/esp32.common.ld
    cmd.exe /C “cd /D D:\Espressif\Projects\examples\get-started\hello_world\VisualGDB\Debug\esp-idf\esp32 && C:\DevTools\VisualGDB\esp-idf\master\tools\ldgen\ldgen.py –config D:/Espressif/Projects/examples/get-started/hello_world/sdkconfig –fragments C:/DevTools/VisualGDB/esp-idf/master/components/soc/linker.lf C:/DevTools/VisualGDB/esp-idf/master/components/heap/linker.lf C:/DevTools/VisualGDB/esp-idf/master/components/xtensa-debug-module/linker.lf C:/DevTools/VisualGDB/esp-idf/master/components/app_trace/linker.lf C:/DevTools/VisualGDB/esp-idf/master/components/freertos/linker.lf C:/DevTools/VisualGDB/esp-idf/master/components/esp_ringbuf/linker.lf C:/DevTools/VisualGDB/esp-idf/master/components/spi_flash/linker.lf C:/DevTools/VisualGDB/esp-idf/master/components/lwip/linker.lf C:/DevTools/VisualGDB/esp-idf/master/components/esp32/linker.lf C:/DevTools/VisualGDB/esp-idf/master/components/esp32/ld/esp32_fragments.lf C:/DevTools/VisualGDB/esp-idf/master/components/espcoredump/linker.lf –input C:/DevTools/VisualGDB/esp-idf/master/components/esp32/ld/esp32.common.ld.in –output D:/Espressif/Projects/examples/get-started/hello_world/VisualGDB/Debug/esp-idf/esp32/esp32.common.ld –sections D:/Espressif/Projects/examples/get-started/hello_world/VisualGDB/Debug/ldgen.section_infos –kconfig C:/DevTools/VisualGDB/esp-idf/master/Kconfig –env “COMPONENT_KCONFIGS= C:/DevTools/VisualGDB/esp-idf/master/components/app_trace/Kconfig C:/DevTools/VisualGDB/esp-idf/master/components/aws_iot/Kconfig C:/DevTools/VisualGDB/esp-idf/master/components/bt/Kconfig C:/DevTools/VisualGDB/esp-idf/master/components/driver/Kconfig C:/DevTools/VisualGDB/esp-idf/master/components/esp32/Kconfig C:/DevTools/VisualGDB/esp-idf/master/components/esp_adc_cal/Kconfig C:/DevTools/VisualGDB/esp-idf/master/components/esp_event/Kconfig C:/DevTools/VisualGDB/esp-idf/master/components/esp_http_client/Kconfig C:/DevTools/VisualGDB/esp-idf/master/components/esp_http_server/Kconfig C:/DevTools/VisualGDB/esp-idf/master/components/esp_https_ota/Kconfig C:/DevTools/VisualGDB/esp-idf/master/components/espcoredump/Kconfig C:/DevTools/VisualGDB/esp-idf/master/components/ethernet/Kconfig C:/DevTools/VisualGDB/esp-idf/master/components/fatfs/Kconfig C:/DevTools/VisualGDB/esp-idf/master/components/freemodbus/Kconfig C:/DevTools/VisualGDB/esp-idf/master/components/freertos/Kconfig C:/DevTools/VisualGDB/esp-idf/master/components/heap/Kconfig C:/DevTools/VisualGDB/esp-idf/master/components/libsodium/Kconfig C:/DevTools/VisualGDB/esp-idf/master/components/log/Kconfig C:/DevTools/VisualGDB/esp-idf/master/components/lwip/Kconfig C:/DevTools/VisualGDB/esp-idf/master/components/mbedtls/Kconfig C:/DevTools/VisualGDB/esp-idf/master/components/mdns/Kconfig C:/DevTools/VisualGDB/esp-idf/master/components/mqtt/Kconfig C:/DevTools/VisualGDB/esp-idf/master/components/nvs_flash/Kconfig C:/DevTools/VisualGDB/esp-idf/master/components/openssl/Kconfig C:/DevTools/VisualGDB/esp-idf/master/components/pthread/Kconfig C:/DevTools/VisualGDB/esp-idf/master/components/spi_flash/Kconfig C:/DevTools/VisualGDB/esp-idf/master/components/spiffs/Kconfig C:/DevTools/VisualGDB/esp-idf/master/components/tcpip_adapter/Kconfig C:/DevTools/VisualGDB/esp-idf/master/components/unity/Kconfig C:/DevTools/VisualGDB/esp-idf/master/components/vfs/Kconfig C:/DevTools/VisualGDB/esp-idf/master/components/wear_levelling/Kconfig” –env “COMPONENT_KCONFIGS_PROJBUILD= C:/DevTools/VisualGDB/esp-idf/master/components/app_update/Kconfig.projbuild C:/DevTools/VisualGDB/esp-idf/master/components/bootloader/Kconfig.projbuild C:/DevTools/VisualGDB/esp-idf/master/components/esptool_py/Kconfig.projbuild C:/DevTools/VisualGDB/esp-idf/master/components/partition_table/Kconfig.projbuild” –env IDF_CMAKE=y –env IDF_PATH=C:/DevTools/VisualGDB/esp-idf/master –env IDF_TARGET=esp32″
    Traceback (most recent call last):
    File “C:\DevTools\VisualGDB\esp-idf\master\tools\ldgen\ldgen.py”, line 22, in <module>
    from fragments import FragmentFileModel
    File “C:\DevTools\VisualGDB\esp-idf\master\tools\ldgen\fragments.py”, line 20, in <module>
    from sdkconfig import SDKConfig
    File “C:\DevTools\VisualGDB\esp-idf\master\tools\ldgen\sdkconfig.py”, line 18, in <module>
    from pyparsing import Word, printables, Combine, Literal, hexnums, quotedString, Optional, nums, removeQuotes, oneOf, Group, infixNotation, opAssoc
    ImportError: No module named pyparsing

     

    #23947
    support
    Keymaster

    Hi,

    Thanks for updating your forum email. This looks like a known bug in the master branch of the ESP-IDF. When building with CMake on Windows, it tries running the Python script directly instead of using the toolchain’s python executable. As a result, the script doesn’t work properly.

    You can reproduce this outside VisualGDB by building the project with idf.py (wrapper for CMake/Ninja build).

    The easiest workaround would be to use GNU Make instead of CMake for affected projects until Espressif fixes the issue.

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.