idf menuconfig in vscode (VSC-1505) #1329
Comments
kotyara12
added
the
bug-report
github-actions
bot
changed the title
|
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 You can also use |
If this worked, would it be necessary to write this issue?
A very inconvenient tool. All elements in a heap, without division into sections. After three scrolls down from the beginning, it is absolutely not clear to which section this or that setting element belongs. |
|
This is what I need (but it's running from pio)
|
|
You are just opening a regular vscode terminal. By running the command
Will improve the UI to have better section separation. |
|
Hi, @brianignacio5!
No, I am not satisfied with this approach at all!!!
Either fix menuconfig or suggest a real way to run menuconfig from a regular command line without tricks. I would have done it myself, but you (the developers) have made an incredible effort to confuse and spoil everything. Firstly, the normal python that is already in the ESP-IDF system does not want to see or know anything about it. Give her your outdated one, and she doesn't want to know about it Secondly, for or three different directories tools, one here, one there, maybe somewhere else Thirdly, when installed, two more pythons are installed, neither of them works A mess in your kingdom. Which is incredibly annoying |
|
Oh, God bless it - with menuconfig... |
Which keys ? Please describe the issue and steps to reproduce it.
How ? What makes it unsuitable ? More detail about it would allow us to identify what needs to be fix.
If you want to use ESP-IDF in any regular terminal outside vscode, please follow the ESP-IDF documentation here: https://docs.espressif.com/projects/esp-idf/en/latest/esp32/get-started/windows-setup.html there is also steps. The 2 python paths used by the extension are: So what is the issue you are facing? You don't want to use |
brianignacio5
changed the title
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 menuconfigand 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 undefinedIs 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
The text was updated successfully, but these errors were encountered: