-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The ESP-IDF path is not installed in the directory which I selected #186
Comments
Thank you @Rainbow-Cai for reporting the issue. The installation consists of two parts:
Note: It's possible to deploy multiple instances of ESP-IDF. It's not necessary to deploy tooling twice. You can pick the directory for tools from E and then deploy new instance of esp-idf to F. Just to be sure that I understand the problem well:
|
Dear @georgik So, can't I deploy the different version SDK tool in the different folder? |
@Rainbow-Cai There is no need to deploy different tooling to different directories. |
@georgik Thanks for your detailed explanation, but to avoid user confusion, it's better to be consistent with user expectations. If users chose another tools path when they install the second ESP-IDF instance, It is better to install it where the user wants, or guide the customer to an existing tools path and tell the reason (eg. Found an existing tool path. Strongly recommended...) |
I used the online installer package to install the Master version of the esp-idf SDK
When I select to install the Master version of esp-idf SDK in my "F:\esp" directory, it will automatically install in my "E:\esp" directory during the installation process. It will installing the "Espressif" files in both my "E:\esp" and "F:\esp" directories at the same time.
As a result, when I install the esp-idf SDK of v5.0 version in the "E:\esp" directory , I cannot use the esp-idf SDK of Master version in "F:\esp" directory at the same time.
My directory structure is as follows:
E:\esp
F:\esp
The error log is in the attachment.
Setup Log 2023-05-22 #009.txt
The text was updated successfully, but these errors were encountered: