- This topic has 7 replies, 2 voices, and was last updated 2 weeks, 3 days ago by
.
-
Posts
-
Hello,
I have updated my machine and i am now evaluating the latest build of visualgdb together with visual studio community 2022. I have migrated one existing esp-idf 5.4 project to the new consolidated toolchain (by manipulating the vgdbproj file no less) and that seems to work, but i have quite alot of projects and not all of them are completely in my hands, so I tried to install/setup the old toolchain style as well (fresh machine). everything seems fine and well but i am unable to build the final python environment, as wheel install seem to fail for me:
Run “C:\Users\Beheerder\AppData\Local\VisualGDB\Python-3.8.10\python.exe C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\idf_tools.py install-python-env” in directory “” on local computer
————————–
Python 3.8.10
pip 25.0.1 from C:\Users\Beheerder\.espressif\python_env\idf5.1_py3.8_env\lib\site-packages\pip (python 3.8)Upgrading pip and setuptools…
Requirement already satisfied: pip in c:\users\beheerder\.espressif\python_env\idf5.1_py3.8_env\lib\site-packages (25.0.1)
Requirement already satisfied: setuptools in c:\users\beheerder\.espressif\python_env\idf5.1_py3.8_env\lib\site-packages (75.3.4)
Skipping the download of C:\Users\Beheerder\.espressif\espidf.constraints.v5.1.txt because it was downloaded recently.
Installing Python packages
Constraint file: C:\Users\Beheerder\.espressif\espidf.constraints.v5.1.txt
Requirement files:
– C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt
Looking in indexes: https://pypi.org/simple, https://dl.espressif.com/pypi
Requirement already satisfied: setuptools in c:\users\beheerder\.espressif\python_env\idf5.1_py3.8_env\lib\site-packages (from -r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 3)) (75.3.4)
Collecting click (from -r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 4))
Using cached https://dl.espressif.com/pypi/click/click-8.1.8-py3-none-any.whl (98 kB)
Collecting pyserial (from -r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 5))
Using cached https://dl.espressif.com/pypi/pyserial/pyserial-3.5-py2.py3-none-any.whl (90 kB)
Collecting cryptography (from -r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 6))
Using cached cryptography-39.0.2-cp36-abi3-win32.whl.metadata (5.8 kB)
Collecting pyparsing (from -r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 7))
Using cached https://dl.espressif.com/pypi/pyparsing/pyparsing-3.0.9-py3-none-any.whl (98 kB)
Collecting pyelftools (from -r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 8))
Using cached https://dl.espressif.com/pypi/pyelftools/pyelftools-0.29-py2.py3-none-any.whl (174 kB)
Collecting idf-component-manager (from -r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 9))
Using cached idf_component_manager-2.4.10-py3-none-any.whl.metadata (9.6 kB)
Collecting esp-coredump (from -r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 10))
Using cached https://dl.espressif.com/pypi/esp-coredump/esp_coredump-1.16.0-py3-none-any.whl (43 kB)
Collecting esptool (from -r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 11))
Using cached esptool-4.11.0-py3-none-any.whl
Collecting esp-idf-kconfig (from -r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 12))
Using cached https://dl.espressif.com/pypi/esp-idf-kconfig/esp_idf_kconfig-1.5.0-py3-none-any.whl (44 kB)
Collecting esp-idf-monitor (from -r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 13))
Using cached https://dl.espressif.com/pypi/esp-idf-monitor/esp_idf_monitor-1.9.0-py3-none-any.whl (58 kB)
Collecting esp-idf-size (from -r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 14))
Using cached https://dl.espressif.com/pypi/esp-idf-size/esp_idf_size-1.7.1-py3-none-any.whl (82 kB)
Collecting freertos_gdb (from -r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 17))
Using cached https://dl.espressif.com/pypi/freertos-gdb/freertos_gdb-1.0.4-py3-none-any.whl (14 kB)
Collecting colorama (from click->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 4))
Using cached https://dl.espressif.com/pypi/colorama/colorama-0.4.6-py2.py3-none-any.whl (25 kB)
Collecting cffi>=1.12 (from cryptography->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 6))
Using cached cffi-1.17.1-cp38-cp38-win32.whl.metadata (1.6 kB)
Collecting psutil (from idf-component-manager->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 9))
Using cached psutil-7.2.2.tar.gz (493 kB)
Installing build dependencies: started
Installing build dependencies: finished with status ‘done’
Getting requirements to build wheel: started
Getting requirements to build wheel: finished with status ‘done’
Preparing metadata (pyproject.toml): started
Preparing metadata (pyproject.toml): finished with status ‘done’
Collecting ruamel.yaml (from idf-component-manager->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 9))
Using cached https://dl.espressif.com/pypi/ruamel-yaml/ruamel_yaml-0.19.1-py3-none-any.whl (118 kB)
Collecting requests (from idf-component-manager->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 9))
Using cached https://dl.espressif.com/pypi/requests/requests-2.33.1-py3-none-any.whl (64 kB)
Collecting requests-file (from idf-component-manager->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 9))
Using cached https://dl.espressif.com/pypi/requests-file/requests_file-3.0.1-py2.py3-none-any.whl (4.5 kB)
Collecting requests-toolbelt (from idf-component-manager->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 9))
Using cached https://dl.espressif.com/pypi/requests-toolbelt/requests_toolbelt-1.0.0-py2.py3-none-any.whl (54 kB)
Collecting tqdm (from idf-component-manager->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 9))
Using cached https://dl.espressif.com/pypi/tqdm/tqdm-4.67.3-py3-none-any.whl (78 kB)
Collecting jsonref (from idf-component-manager->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 9))
Using cached https://dl.espressif.com/pypi/jsonref/jsonref-1.1.0-py3-none-any.whl (9.4 kB)
Collecting pydantic!=2.12.0 (from idf-component-manager->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 9))
Using cached https://dl.espressif.com/pypi/pydantic/pydantic-2.12.5-py3-none-any.whl (463 kB)
Collecting pydantic-core (from idf-component-manager->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 9))
Using cached pydantic_core-2.27.2-cp38-cp38-win32.whl.metadata (6.7 kB)
Collecting pydantic-settings (from idf-component-manager->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 9))
Using cached https://dl.espressif.com/pypi/pydantic-settings/pydantic_settings-2.13.1-py3-none-any.whl (58 kB)
Collecting typing-extensions (from idf-component-manager->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 9))
Using cached https://dl.espressif.com/pypi/typing-extensions/typing_extensions-4.15.0-py3-none-any.whl (44 kB)
Collecting construct~=2.10 (from esp-coredump->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 10))
Using cached https://dl.espressif.com/pypi/construct/construct-2.10.70-py3-none-any.whl (63 kB)
Collecting pygdbmi>=0.9.0.2 (from esp-coredump->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 10))
Using cached https://dl.espressif.com/pypi/pygdbmi/pygdbmi-0.9.0.2-py3-none-any.whl (16 kB)
Collecting bitstring!=4.2.0,>=3.1.6 (from esptool->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 11))
Using cached https://dl.espressif.com/pypi/bitstring/bitstring-4.4.0-py3-none-any.whl (76 kB)
Collecting ecdsa>=0.16.0 (from esptool->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 11))
Using cached https://dl.espressif.com/pypi/ecdsa/ecdsa-0.19.2-py2.py3-none-any.whl (150 kB)
Collecting reedsolo<1.8,>=1.5.3 (from esptool->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 11))
Using cached https://dl.espressif.com/pypi/reedsolo/reedsolo-1.7.0-py3-none-any.whl (32 kB)
Collecting PyYAML>=5.1 (from esptool->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 11))
Using cached PyYAML-6.0.3-cp38-cp38-win32.whl.metadata (2.2 kB)
Collecting intelhex (from esptool->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 11))
Using cached https://dl.espressif.com/pypi/intelhex/intelhex-2.3.0-py2.py3-none-any.whl (50 kB)
Collecting kconfiglib>=13.7.1 (from esp-idf-kconfig->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 12))
Using cached https://dl.espressif.com/pypi/kconfiglib/kconfiglib-14.1.0-py2.py3-none-any.whl (145 kB)
Collecting windows-curses (from esp-idf-kconfig->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 12))
Using cached windows_curses-2.4.2-cp38-cp38-win32.whl.metadata (2.8 kB)
Collecting esp-idf-panic-decoder~=1.4 (from esp-idf-monitor->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 13))
Using cached https://dl.espressif.com/pypi/esp-idf-panic-decoder/esp_idf_panic_decoder-1.5.0-py3-none-any.whl (21 kB)
Collecting rich (from esp-idf-size->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 14))
Using cached https://dl.espressif.com/pypi/rich/rich-15.0.0-py3-none-any.whl (310 kB)
Collecting bitarray<4.0,>=3.0.0 (from bitstring!=4.2.0,>=3.1.6->esptool->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 11))
Using cached bitarray-3.8.1-cp38-cp38-win32.whl.metadata (35 kB)
Collecting tibs<0.6,>=0.5.6 (from bitstring!=4.2.0,>=3.1.6->esptool->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 11))
Using cached tibs-0.5.7-cp38-abi3-win32.whl.metadata (8.3 kB)
Collecting pycparser (from cffi>=1.12->cryptography->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 6))
Using cached https://dl.espressif.com/pypi/pycparser/pycparser-3.0-py3-none-any.whl (48 kB)
Collecting six>=1.9.0 (from ecdsa>=0.16.0->esptool->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 11))
Using cached https://dl.espressif.com/pypi/six/six-1.17.0-py2.py3-none-any.whl (11 kB)
Collecting annotated-types>=0.6.0 (from pydantic!=2.12.0->idf-component-manager->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 9))
Using cached https://dl.espressif.com/pypi/annotated-types/annotated_types-0.7.0-py3-none-any.whl (13 kB)
INFO: pip is looking at multiple versions of pydantic to determine which version is compatible with other requirements. This could take a while.
Collecting pydantic!=2.12.0 (from idf-component-manager->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 9))
Using cached https://dl.espressif.com/pypi/pydantic/pydantic-2.12.3-py3-none-any.whl (462 kB)
Using cached https://dl.espressif.com/pypi/pydantic/pydantic-2.10.6-py3-none-any.whl (431 kB)
INFO: pip is looking at multiple versions of typing-extensions to determine which version is compatible with other requirements. This could take a while.
Collecting typing-extensions (from idf-component-manager->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 9))
Using cached https://dl.espressif.com/pypi/typing-extensions/typing_extensions-4.13.2-py3-none-any.whl (45 kB)
Collecting python-dotenv>=0.21.0 (from pydantic-settings->idf-component-manager->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 9))
Using cached https://dl.espressif.com/pypi/python-dotenv/python_dotenv-1.2.2-py3-none-any.whl (22 kB)
Collecting typing-inspection>=0.4.0 (from pydantic-settings->idf-component-manager->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 9))
Using cached https://dl.espressif.com/pypi/typing-inspection/typing_inspection-0.4.2-py3-none-any.whl (14 kB)
INFO: pip is looking at multiple versions of pydantic-settings to determine which version is compatible with other requirements. This could take a while.
Collecting pydantic-settings (from idf-component-manager->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 9))
Using cached https://dl.espressif.com/pypi/pydantic-settings/pydantic_settings-2.13.0-py3-none-any.whl (58 kB)
Using cached https://dl.espressif.com/pypi/pydantic-settings/pydantic_settings-2.12.0-py3-none-any.whl (51 kB)
Using cached https://dl.espressif.com/pypi/pydantic-settings/pydantic_settings-2.11.0-py3-none-any.whl (48 kB)
Using cached https://dl.espressif.com/pypi/pydantic-settings/pydantic_settings-2.8.1-py3-none-any.whl (30 kB)
Collecting charset_normalizer<4,>=2 (from requests->idf-component-manager->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 9))
Using cached charset_normalizer-3.4.7-cp38-cp38-win32.whl.metadata (41 kB)
Collecting idna<4,>=2.5 (from requests->idf-component-manager->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 9))
Using cached idna-3.14-py3-none-any.whl.metadata (8.0 kB)
Collecting urllib3<3,>=1.26 (from requests->idf-component-manager->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 9))
Using cached https://dl.espressif.com/pypi/urllib3/urllib3-1.26.20-py2.py3-none-any.whl (144 kB)
Collecting certifi>=2023.5.7 (from requests->idf-component-manager->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 9))
Using cached certifi-2026.4.22-py3-none-any.whl.metadata (2.5 kB)
INFO: pip is looking at multiple versions of requests to determine which version is compatible with other requirements. This could take a while.
Collecting requests (from idf-component-manager->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 9))
Using cached https://dl.espressif.com/pypi/requests/requests-2.32.5-py3-none-any.whl (64 kB)
Using cached https://dl.espressif.com/pypi/requests/requests-2.32.4-py3-none-any.whl (64 kB)
Collecting markdown-it-py>=2.2.0 (from rich->esp-idf-size->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 14))
Using cached https://dl.espressif.com/pypi/markdown-it-py/markdown_it_py-4.0.0-py3-none-any.whl (87 kB)
Collecting pygments<3.0.0,>=2.13.0 (from rich->esp-idf-size->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 14))
Using cached https://dl.espressif.com/pypi/pygments/pygments-2.20.0-py3-none-any.whl (1.2 MB)
INFO: pip is looking at multiple versions of rich to determine which version is compatible with other requirements. This could take a while.
Collecting rich (from esp-idf-size->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 14))
Using cached https://dl.espressif.com/pypi/rich/rich-14.3.4-py3-none-any.whl (310 kB)
INFO: pip is looking at multiple versions of ruamel-yaml to determine which version is compatible with other requirements. This could take a while.
Collecting ruamel.yaml (from idf-component-manager->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 9))
Using cached https://dl.espressif.com/pypi/ruamel-yaml/ruamel.yaml-0.18.16-py3-none-any.whl (119 kB)
Collecting ruamel.yaml.clib>=0.2.7 (from ruamel.yaml->idf-component-manager->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 9))
Using cached ruamel.yaml.clib-0.2.8-cp38-cp38-win32.whl.metadata (2.3 kB)
Collecting mdurl~=0.1 (from markdown-it-py>=2.2.0->rich->esp-idf-size->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 14))
Using cached https://dl.espressif.com/pypi/mdurl/mdurl-0.1.2-py3-none-any.whl (10.0 kB)
INFO: pip is looking at multiple versions of markdown-it-py to determine which version is compatible with other requirements. This could take a while.
Collecting markdown-it-py>=2.2.0 (from rich->esp-idf-size->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 14))
Using cached https://dl.espressif.com/pypi/markdown-it-py/markdown_it_py-3.0.0-py3-none-any.whl (87 kB)
INFO: pip is looking at multiple versions of pygments to determine which version is compatible with other requirements. This could take a while.
Collecting pygments<3.0.0,>=2.13.0 (from rich->esp-idf-size->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 14))
Using cached https://dl.espressif.com/pypi/pygments/pygments-2.19.2-py3-none-any.whl (1.2 MB)
INFO: pip is looking at multiple versions of python-dotenv to determine which version is compatible with other requirements. This could take a while.
Collecting python-dotenv>=0.21.0 (from pydantic-settings->idf-component-manager->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 9))
Using cached https://dl.espressif.com/pypi/python-dotenv/python_dotenv-1.2.1-py3-none-any.whl (21 kB)
Using cached https://dl.espressif.com/pypi/python-dotenv/python_dotenv-1.0.1-py3-none-any.whl (19 kB)
INFO: pip is looking at multiple versions of pycparser to determine which version is compatible with other requirements. This could take a while.
Collecting pycparser (from cffi>=1.12->cryptography->-r C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\requirements\requirements.core.txt (line 6))
Using cached https://dl.espressif.com/pypi/pycparser/pycparser-2.23-py3-none-any.whl (118 kB)
Using cached cryptography-39.0.2-cp36-abi3-win32.whl (2.1 MB)
Using cached idf_component_manager-2.4.10-py3-none-any.whl (177 kB)
Using cached cffi-1.17.1-cp38-cp38-win32.whl (171 kB)
Using cached pydantic_core-2.27.2-cp38-cp38-win32.whl (1.8 MB)
Using cached PyYAML-6.0.3-cp38-cp38-win32.whl (143 kB)
Using cached windows_curses-2.4.2-cp38-cp38-win32.whl (76 kB)
Using cached bitarray-3.8.1-cp38-cp38-win32.whl (143 kB)
Using cached certifi-2026.4.22-py3-none-any.whl (135 kB)
Using cached charset_normalizer-3.4.7-cp38-cp38-win32.whl (142 kB)
Using cached idna-3.14-py3-none-any.whl (72 kB)
Using cached ruamel.yaml.clib-0.2.8-cp38-cp38-win32.whl (100 kB)
Using cached tibs-0.5.7-cp38-abi3-win32.whl (288 kB)
Building wheels for collected packages: psutil
Building wheel for psutil (pyproject.toml): started
Building wheel for psutil (pyproject.toml): finished with status ‘error’
error: subprocess-exited-with-errorBuilding wheel for psutil (pyproject.toml) did not run successfully.
exit code: 1[23 lines of output]
running bdist_wheel
running build
running build_py
creating build\lib.win32-cpython-38\psutil
copying psutil\_common.py -> build\lib.win32-cpython-38\psutil
copying psutil\_ntuples.py -> build\lib.win32-cpython-38\psutil
copying psutil\_psaix.py -> build\lib.win32-cpython-38\psutil
copying psutil\_psbsd.py -> build\lib.win32-cpython-38\psutil
copying psutil\_pslinux.py -> build\lib.win32-cpython-38\psutil
copying psutil\_psosx.py -> build\lib.win32-cpython-38\psutil
copying psutil\_psposix.py -> build\lib.win32-cpython-38\psutil
copying psutil\_pssunos.py -> build\lib.win32-cpython-38\psutil
copying psutil\_pswindows.py -> build\lib.win32-cpython-38\psutil
copying psutil\__init__.py -> build\lib.win32-cpython-38\psutil
running build_ext
building ‘psutil._psutil_windows’ extension
creating build\temp.win32-cpython-38\Release\psutil
creating build\temp.win32-cpython-38\Release\psutil\arch\all
creating build\temp.win32-cpython-38\Release\psutil\arch\windows
“C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.44.35207\bin\HostX86\x86\cl.exe” /c /nologo /O2 /W3 /GL /DNDEBUG /MD -DPSUTIL_SIZEOF_PID_T=4 -DPSUTIL_VERSION=722 -DPy_LIMITED_API=0x03070000 -DPSUTIL_WINDOWS=1 -D_WIN32_WINNT=0x01000 -D_AVAIL_WINVER_=0x01000 -D_CRT_SECURE_NO_WARNINGS -DPSAPI_VERSION=1 -IC:\Users\Beheerder\.espressif\python_env\idf5.1_py3.8_env\include -IC:\Users\Beheerder\AppData\Local\VisualGDB\Python-3.8.10\include -IC:\Users\Beheerder\AppData\Local\VisualGDB\Python-3.8.10\Include “-IC:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.44.35207\include” “-IC:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.44.35207\ATLMFC\include” “-IC:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\VS\include” “-IC:\Program Files (x86)\Windows Kits\NETFXSDK\4.8\include\um” /Tcpsutil/_psutil_windows.c /Fobuild\temp.win32-cpython-38\Release\psutil/_psutil_windows.obj
_psutil_windows.c
C:\Users\Beheerder\AppData\Local\VisualGDB\Python-3.8.10\include\pyconfig.h(59): fatal error C1083: Cannot open include file: ‘io.h’: No such file or directory
error: command ‘C:\\Program Files\\Microsoft Visual Studio\\2022\\Community\\VC\\Tools\\MSVC\\14.44.35207\\bin\\HostX86\\x86\\cl.exe’ failed with exit code 2
[end of output]note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for psutil
Failed to build psutil
ERROR: Failed to build installable wheels for some pyproject.toml based projects (psutil)
Traceback (most recent call last):
File “C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\idf_tools.py”, line 2687, in <module>
main(sys.argv[1:])
File “C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\idf_tools.py”, line 2679, in main
action_func(args)
File “C:\SysGCC\esp32__V5_1\esp-idf\v5.1\tools\idf_tools.py”, line 2139, in action_install_python_env
subprocess.check_call(run_args, stdout=sys.stdout, stderr=sys.stderr, env=env_copy)
File “C:\Users\Beheerder\AppData\Local\VisualGDB\Python-3.8.10\lib\subprocess.py”, line 364, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command ‘[‘C:\\Users\\Beheerder\\.espressif\\python_env\\idf5.1_py3.8_env\\Scripts\\python.exe’, ‘-m’, ‘pip’, ‘install’, ‘–no-warn-script-location’, ‘-r’, ‘C:\\SysGCC\\esp32__V5_1\\esp-idf\\v5.1\\tools\\requirements\\requirements.core.txt’, ‘–upgrade’, ‘–constraint’, ‘C:\\Users\\Beheerder\\.espressif\\espidf.constraints.v5.1.txt’, ‘–extra-index-url’, ‘https://dl.espressif.com/pypi’%5D’ returned non-zero exit status 1.
————————–
Command exited with code 1this way of working was consistent on my previous work machine and does not require us to change the project files. I have also tried to remove the python folders as described in the tutorial file. but nothing seems to be passing this final step. is there any possibility that this way of working can be combined with the consolidated toolchain? im evaluating the trial version right now
Hi,
This looks like some Python dependencies are broken. If you are using an old ESP-IDF and old Python, the packages it requires may not be available anymore. You can try still selecting this ESP-IDF version in the new consolidated mode. It will use the Python package shipped by Espressif, that might work better.
i did the following:
- opened an old project on release/v5.1 in visual studio 2022, this is broken since no old toolchain has ever been completed successful
- I found the v5.1 branch in the espressif github and managed to install the consolidated toolchain for this release;
- Then in the project properties i was able to change the project to this consolidated toolchain
- when reopening this project in vs it picked up the change, asked me to retarget to v5.1.1 and building failed
Removing C:\Users\Beheerder\Documents\Espressif\Solutions\CP719\CP719_1/build/VisualGDB/Debug…
Run “C:\Users\Beheerder\AppData\Local\VisualGDB\CMake\bin\cmake.exe ../../.. -G “Ninja” -DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_MAKE_PROGRAM=C:/Users/Beheerder/.espressif/tools/ninja/1.12.1/ninja.exe -DESP_PLATFORM=1 -DCCACHE_ENABLE=0″ in directory “C:\Users\Beheerder\Documents\Espressif\Solutions\CP719\CP719_1/build/VisualGDB/Debug” on local computer
C:\Users\Beheerder\AppData\Local\VisualGDB\CMake\bin\cmake.exe ../../.. -G “Ninja” -DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_MAKE_PROGRAM=C:/Users/Beheerder/.espressif/tools/ninja/1.12.1/ninja.exe -DESP_PLATFORM=1 -DCCACHE_ENABLE=0
— IDF_TARGET is not set, guessed ‘esp32’ from sdkconfig ‘C:/Users/Beheerder/Documents/Espressif/Solutions/CP719/CP719_1/sdkconfig’
— Found Git: C:/Users/Beheerder/.espressif/tools/idf-git/2.39.2/cmd/git.exe (found version “2.39.2.windows.1”)
— The C compiler identification is GNU 12.2.0
— The CXX compiler identification is GNU 12.2.0
— The ASM compiler identification is GNU
— Found assembler: C:/Users/Beheerder/.espressif/tools/xtensa-esp32-elf/esp-12.2.0_20230208/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc.exe
— Detecting C compiler ABI info
— Detecting C compiler ABI info – done
— Check for working C compiler: C:/Users/Beheerder/.espressif/tools/xtensa-esp32-elf/esp-12.2.0_20230208/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc.exe – skipped
— Detecting C compile features
— Detecting C compile features – done
— Detecting CXX compiler ABI info
— Detecting CXX compiler ABI info – done
— Check for working CXX compiler: C:/Users/Beheerder/.espressif/tools/xtensa-esp32-elf/esp-12.2.0_20230208/xtensa-esp32-elf/bin/xtensa-esp32-elf-g++.exe – skipped
— Detecting CXX compile features
— Detecting CXX compile features – done
— Building ESP-IDF components for target esp32
— Checking Python dependencies…
pkg_resources cannot be imported. The most common cause is a missing pip or setuptools package. If you’ve installed a custom Python then these packages are provided separately and have to be installed as well. Please refer to the Get Started section of the ESP-IDF Programming Guide for setting up the required packages.
Constraint file: C:\Users\Beheerder\.espressif\espidf.constraints.v5.1.txt
Requirement files:
– C:\Users\Beheerder\esp-idf\v5.1\esp-idf\tools\requirements\requirements.core.txt
Python being checked: C:\Users\Beheerder\.espressif\python_env\\idf5.1_py3.11_env\Scripts\python.exe
CMake Error at C:/Users/Beheerder/esp-idf/v5.1/esp-idf/tools/cmake/build.cmake:366 (message):
Failed to run Python dependency check. Python: python, Error: -1
Call Stack (most recent call first):
C:/Users/Beheerder/esp-idf/v5.1/esp-idf/tools/cmake/build.cmake:498 (__build_check_python)
C:/Users/Beheerder/esp-idf/v5.1/esp-idf/tools/cmake/project.cmake:464 (idf_build_process)
CMakeLists.txt:8 (project)— Configuring incomplete, errors occurred!
————————————————————-
Command exited with code 1
Executable: C:\Users\Beheerder\AppData\Local\VisualGDB\CMake\bin\cmake.exe
Arguments: ../../.. -G “Ninja” -DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_MAKE_PROGRAM=C:/Users/Beheerder/.espressif/tools/ninja/1.12.1/ninja.exe -DESP_PLATFORM=1 -DCCACHE_ENABLE=0
Directory: C:\Users\Beheerder\Documents\Espressif\Solutions\CP719\CP719_1/build/VisualGDB/Debug
Command-line action failed========== Project Rebuild Summary ==========
CP719_1 rebuilt in 00:05
========== Rebuild: 0 Succeeded, 1 Failed, 0 Skipped ==========im confused, the gui to download all this told me the python requirement is satisfied (python 3.11) but it still complaining, do I install python separate as well?
i cannot open any visual gdb project made prior to consolidated toolchain
i cannot start a new project from any branch from consolidated toolchain
documentation seems straightforward but it is not and seem easy to miss something important
Hi,
This still looks like some Python package issues. According to Espressif, ESP-IDF 5.1 reached the end of life last December, so they could have taken down some packages.
You can try doing a clean test by deleting the C:/Users/Beheerder/esp-idf and C:/Users/Beheerder/.espressif directories, downloading that ESP-IDF version again using the consolidated GUI, and creating a new project from scratch.
If that doesn’t work either, you can try creating a project using the Espressif’s VS Code extension. If that one fails with the same error, you would need to check with Espressif regarding workarounds.
i cannot get the consolidated toolchain too work.
I attempted with the packaged gnu toolchain
I tried with combination of visual studio 2022, visualgdb 6.1 and the IDF 5.1; esp32-20230208 gnu toolchain, on windows 11 Pro 25H2
my installation root of this toolchain is “C:\SysGCC\esp32__V5_1__GCC_12_2_0” (not the expected default esp32 folder, is this somehow important)
- helloworld project, failed with error similar to the one in my first post
- existing original project from me, failed with error similar to the one in my first post
this is after two consecutive reinstalls of all these tools mentioned. on a fresh machine. How can I solve this? Is the packaged toolchain not supposed to decouple from rapid tooling changes? and how can it still miss dependencies? this is the message explaining where it failed
C:\Users\Beheerder\AppData\Local\VisualGDB\Python-3.8.10\include\pyconfig.h(59): fatal error C1083: Cannot open include file: ‘io.h’: No such file or directorydo i need to install python myself and point it towards that installation? im not sure and could not find any conclusive
This is a weird and really unexpected problem, since I wish to evaluate going further with visualgdb (had good experience with this toolchain on my previous machine, where it all worked very well) and i did not expect too be stuck in the basic installation
from the first error message i notice
Hi,
This error means that the toolchain depends on some Python packages that have been discontinued. As a workaround, Python tries to build them from sources, and that doesn’t work due to some reason. Perhaps it needs additional dependencies, perhaps the package was never meant to be built on Windows. We don’t have any additional insights into this particular package.
We understand your frustration, but this is really not up to VisualGDB. VisualGDB can run “pip install” to install the dependencies, but if the dependencies have been discontinued by their maintainers, VisualGDB cannot automatically make them appear in the repository.
This is the main reason why VisualGDB, and its CMake framework (e.g. used for STM32) is built without Python packages and does not depend on any downloadable dependencies. However, we cannot make every hardware vendor do the same. Espressif did switch to somewhat better layout with virtual environments and newer Python versions, but ESP-IDF 5.1 is an old discontinued release. It might be just dead in the water at this point.
Our best advice would be to find the oldest ESP-IDF version that still works, and try upgrading the project to it. If you want to keep using it beyond the end-of-life date, please consider making a VM with all the necessary tools to avoid disruptions like this.
- You must be logged in to reply to this topic.