-
Notifications
You must be signed in to change notification settings - Fork 7.5k
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
crosstool-ng version esp-2022r1 doesn't match supported version esp-2022r1-RC1 (IDFGH-8404) #9870
Comments
It looks like some installation step was missed, and the environment variables in Eclipse are still pointing to the newer toolchain used in the @ddomnik just a question, why do you need to switch to |
@igrr thanks for the fast reply. We want to develop under the v5.1-dev tag. Using master was just a result of a new clean install via the Windows installer. Edit:
|
Hello @ddomnik When you switch idf versions it's recommended to run the project full clean command -
|
If you still have a problem, please share the Install tools console log and product information log |
hello @kolipakakondal the full clean command did not solve the problem. Install tools log after fullclean:
Product information:
Install tools logs after ESp-IDF Tool Manager > Install tools:
|
Please make sure you understand the purpose of this tag. It is not a release tag, it just indicates the point where development of v5.1 is started. It is not recommended to use such tags for product development. Generally, we won't provide support for issues you may encounter for such a tag. It's better to use a stable release or a release branch for development. More information about the releases is available at https://docs.espressif.com/projects/esp-idf/en/latest/esp32/versions.html#which-version-should-i-start-with. |
Thank you for the detailed information regarding this. In that case we will stay with our current version and will not update to the 5.1-dev tag. Regarding that, is there any date planned for the stable v5.0 release tag? Thanks |
Thanks @ddomnik for sharing logs. Looks like I don't see any issue in installing tools at least looking at the logs, then the problem might be in the esp-idf selection while installing tools.
esp-idf However, as recommended by Ivan, please stick to the stable releases. |
I can't give you a specific date, unfortunately. Our QA test has found a number of issues in v5.0-beta1 release and currently we are working on fixing them. This might take a few weeks to do the fixes and verify them. |
|
Agree with you. We will work on this. We could maintain the relative path (relative to IDF_PATH and .espressif folder) for the Location, working directory, and arguments section in the launch configuration wizard so that when the user switches between IDF versions and systems, the launch configuration doesn't need to make any changes. For our internal reference https://jira.espressif.com:8443/browse/IEP-837 |
As we have implemented dynamic variables for the esp-idf verison in the espressif-ide, we can close this issue. ![]() |
Answers checklist.
IDF version.
012fafb (HEAD, tag: v5.1-dev)
Operating System used.
Windows
How did you build your project?
Eclipse IDE
If you are using Windows, please specify command line type.
PowerShell
What is the expected behavior?
Complete installation ready to build.
What is the actual behavior?
Switching from master to the tag v5.1-dev results in the following error when building the project using Eclipse.
Steps to reproduce.
Build or installation Logs.
No response
More Information.
No response
The text was updated successfully, but these errors were encountered: