-
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
3.0.x incompatibilities #9802
Comments
@habazut - There are many ways to keep using the ESP32 Arduino 2.0.x Core: 3.0.x is a major version change that has breaking changes as already said. This new version is indeed improving the API and preparing space for the new Espressif SoC that were and will be launched. 2.0.x is the former one. We've just released 2.0.17 with bug fixes. We may not release new 2.0.x packages in the future.
Please tell us more about the |
Automatic as in |
@Lucasczm - Could you please help this issue? @habazut wants to use Regarding the effort for migrating a code from 2.0.x to 3.0.x, there is a document: |
I think what @habazut meant is that when run the arduino-cli core uninstall esp32:esp32
arduino-cli core install esp32:[email protected] You can also use PlatformIO, where you can configure the Arduino core version in each project @lucasssvaz - I think you were the one who should be mentioned |
@Lucasczm - Thanks!! Very kind of you. |
Migration guide is linked above, 2.X version is still available. We tried to reduce breaking changes for v3.x as much as possible but there are still some which are necessary to support new SoCs and features and this cannot be avoided in general in Software development. Changes are described in Migration Guide and we are also here to help you moving your current projects. As there is no action in this particular ticket, I am closing it as answered, if needed you can reopen the issue. Thanks for understanding |
Board
ALL
Device Description
Not relevant
Hardware Configuration
Not relevant
Version
v3.0.1
IDE Name
Arduino IDE
Operating System
ALL
Flash frequency
not relevant
PSRAM enabled
yes
Upload speed
not relevant
Description
As stated in #8796 you want new issue instead of buinding on the existing. Here you go.
Users have made you aware of the incompatibilities of the 3.0.x version a long time ago. For example here:
#8780
With your rollout of the 3.0.0 as an AUTOMATIC upgrade from 2.0.x you did cause a lot of extra work as a lot of code does not compile any more and then the user complains to the project which is only using your API and not to you who are responsible for the change. That is a major pain. You did issue the rollout in spite of the incompatibility. The 3.0.0 HAL is so different it could as well been another CPU architecture.
This above issue from 2023 shows you were very well aware that the 3.0.0 upgrade was a BREAKING change and nevertheless you did roll it out as an automatic upgrade.
It would have given the world much less grief if you would have created a new package (say esp32:idf5) instead of pretending that
esp32:[email protected]
is an upgrade toesp32:[email protected]
, a fact that you very well were aware of.To be clear:
I am NOT complaining about the ESP-IDF API that you do have no control of (as mentioned in #8780)
I am complaining that you have rolled this out as an AUTOMATIC upgrade in spite that as you have admitted you have NO CONTROL OF THE INCOMPATIBILITIES and you were WELL AWARE ABOUT IT.
I would not like want to treat the users of the projetcs where I feel responsible in this way.
Sketch
Debug Message
Other Steps to Reproduce
No response
I have checked existing issues, online documentation and the Troubleshooting Guide
The text was updated successfully, but these errors were encountered: