Open kotyara12 opened 8 hours ago
Your settings seems to be correct, the thing is that when you open a terminal in vscode, the environment variables from the extension are not loaded.
To achieve that, run the ESP-IDF: Open ESP-IDF Terminal
command (menu View
-> Command Palette -> Type open esp-idf terminal
) which will create a new terminal with ESP-IDF settings loaded then idf.py menuconfig
should work.
You can also use ESP-IDF: SDK Configuration editor
to open a UI version of idf.py menuconfig with search functionality.
OS
Windows
Operating System version
Windows 10
Visual Studio Code version
1.94.2
ESP-IDF version
5.3.1
Python version
3.11.2
Doctor command output
Extension
No response
Description
Installed the ESP-IDF extension on Windows.
I chose the IDF_PATH directory as
C:\Projects\Espressif\esp-idf
, IDF_TOOL_PATHc:\Soft\Espressif\
From VS Code, something works somehow somewhere.
BUT! I am absolutely not satisfied with the configuration editor built into the plugin. It is extremely inconvenient and uninformative. I am also absolutely satisfied with the option in the text window, like in platformio (pio run -t sdkconfig)
ok. we call the cmd interpreter and type the command as written in your instructions:
idf.py menuconfig
and we get a complete ass. nothing works. the system does not understand what py is, where to look for it, and in general what kind of crap it is and how to eat it.
okay. let's start figuring it out. There are many more questions than answers.
Firstly, the tools directory is in both IDF_PATH and IDF_TOOL_PATH!!! Why? Well, screw them.
Secondly, Python was installed twice:
But it CANNOT BE LAUNCHED from the command line ANYWHERE! Instead of the interpreter, the Windows store opens. And the doctor command gives out
System environment variable IDF_PYTHON_ENV_PATH undefined
Is this a normal installation?????Thirdly, IDF_PATH and IDF_TOOL_PATH are only available inside VSCode. When called from the command line, nothing is configured and nothing works. How the hell is that possible? An attempt to execute exports.sh complains that there is no python in the system. But you installed it twice, damn it????
An attempt to manually register environment variables gave absolutely nothing.
I can try to fix something with my hands, but what??? Reading kilometers of forums for years in useless attempts to fix something....Yes, this is a real pleasure
Debug Message
Other Steps to Reproduce
I have checked existing issues, online documentation and the Troubleshooting Guide