Skip to content

Barely installing this board causes sketches for unrelated board to fail to compile #2137

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

Closed
teo1978 opened this issue Dec 2, 2018 · 8 comments
Labels
Status: Stale Issue is stale stage (outdated/stuck)

Comments

@teo1978
Copy link

teo1978 commented Dec 2, 2018

I installed the ESP32 cores on the Arduino IDE via the Board Manager.

Then I opened a sketch that uses another board, the ESP8266 Thing Dev from SparkFun, which is one of the board in a separate package: https://github.com/esp8266/Arduino.

This sketch used to complie just fine. The old board is still selected, I am trying to compile the sketch (which I haven't touched) for the same ESP8266 as before. That is, I am not even using the ESP32 core I just installed.

Yet I get compile errors like this:

Error compiling for board SparkFun ESP8266 Thing Dev.
fork/exec /home/teo/.arduino15/packages/esp32/tools/esptool/2.3.1/esptool: no such file or directory
Error compiling for board SparkFun ESP8266 Thing Dev.

Basically, merely installing the ESP32 board backage has messed with the preexisting ESP8266 package that was previously installed and worked fine before. Obviously I should be able to have both installed ans working.

@teo1978
Copy link
Author

teo1978 commented Dec 2, 2018

Also, when removing the ESP32 board, a NullPointerException showed up (though they seem to have been removed succesfully):

image

@teo1978
Copy link
Author

teo1978 commented Dec 2, 2018

And now, after (supposedly) removing the board, sketches compiled for the Sparkfun ESP8266 board (which should never have been affected in the slightest in the first place) now behave strangely. The board cannot connect to wifi anymore. It keeps saying "scandone" and "reconnect" debug messages while trying to connect to the wifi network. It never showed this behavior before, and I haven't touched the ESP8266 cores (haven't updated them, I have the same version that always worked), nor of course my code.

The extent to which just installing this board (without even attempting to use it) has screwed up with my Arduino installation is appalling.

Maybe part of this is bugs from Arduino itself (e.g. the part where several files from this fucked up board are still present in my system after I have used the Board Manager to remove it). Please report to them whatever parts of the issues are their fault.

@lbernstone
Copy link
Contributor

I understand your frustration, but the esp32 board package installs nothing outside of the .arduino15/packages/esp32 directory. Any interference with another board's core files is entirely an arduino IDE issue. I regularly use esp8266 and esp32 to compile without issues.
Good luck

@teo1978
Copy link
Author

teo1978 commented Dec 3, 2018

Please have a loot at the response from the Arduino team:
arduino/Arduino#8258 (comment)

From what I understand, there is a fundamental design flaw in the Arduino IDE, but also an error on your side, or at least a trivial workaround that you could apply to easily avoid the issue completely.

@lbernstone
Copy link
Contributor

lbernstone commented Dec 3, 2018

Ok, I'll take a look.

@teo1978
Copy link
Author

teo1978 commented Dec 3, 2018

It may be that the issue only arises if one of the board packages (e.g. esp8266) is installed directly into arduino's program folder (which, as far as I understand, is what you do when you want to install the most recent version from github as opposed to the latest stable release) while the other (e.g. esp32) is installed via the Board Manager which installs it into ~/.arduinosomething. I don't know if, by installing both in the same way, everything would work.

@stale
Copy link

stale bot commented Aug 1, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Status: Stale Issue is stale stage (outdated/stuck) label Aug 1, 2019
@stale
Copy link

stale bot commented Aug 15, 2019

This stale issue has been automatically closed. Thank you for your contributions.

@stale stale bot closed this as completed Aug 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Stale Issue is stale stage (outdated/stuck)
Projects
None yet
Development

No branches or pull requests

2 participants