-
Notifications
You must be signed in to change notification settings - Fork 13.3k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Eclipse Sloeber - cannot build using 3.1.0 #8803
Comments
#8804 should fix that, assuming the issue is with locally-installed python <3.7 What happens with Sloeber is whole other thing. Searching in the issue tracker, there is a mention of stm32duino (which is similar to the implementation of build options here) But, exception for stm32duino in tests is removed in the current version... so, it works? I wonder what our differences, then. |
workaround: in platform.sloeber.txt change and this could be the fix in platform.txt too |
Note that if you do the workaround as described above you also need to do the following steps to clear the caching |
After more investigation in this issue my proposed workaround is to comment out the following line in the platform.txt and execute the cache clearing steps Sloeber/arduino-eclipse-plugin#1533 This is a better solution because Sloeber uses the build command for discovery purposes. As the discovery is triggered early on it is very unlikely the build has run before the discovery runs. Therefore the opt file is missing and the discovery fails. |
I'm glad to see this got fixed |
For all struggling with this error: |
Hello,
https://arduino.esp8266.com/stable/package_esp8266com_index.json
to the third party tabon the arduino IDE i make the exact same steps for installing the 3.1.0 board manager and i tried again to compile the blink sketch. The results are these
the 3.0.2 version of the boards manager works perfectly on both sloeber and arduino IDE
The text was updated successfully, but these errors were encountered: