Skip to content

Arduino IDE selects wrong board package toolchain #5042

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.

Sign up for GitHub

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

Jump to bottom
Closed
vshymanskyy opened this issue Jun 15, 2016 · 4 comments · Fixed by #5199
Closed

Arduino IDE selects wrong board package toolchain #5042

vshymanskyy opened this issue Jun 15, 2016 · 4 comments · Fixed by #5199
Milestone
Release 1.6.11

Comments

@vshymanskyy
Copy link

The Arduino IDE (or arduino-builder), selects the wrong toolchain when some additional platforms are installed through Boards Manager.

For example, if I install both Digistump Oak and ESP8266 community packages, it selects
.arduino15/packages/digistump/tools/xtensa-lx106-elf-gcc instead of
.arduino15/packages/esp8266/tools/xtensa-lx106-elf-gcc when compiling for regular ESP8266.

It causes more problems like this:
I'm trying to build "Blink" example for MKR100 (after installing RedBear Duo support package):
It fails, because IDE selects ~/.arduino15/packages/RedBear/tools/arm-none-eabi-gcc/4.9-2015-q3 toolchain, and it's not compiling correctly.

Same for some other boards combinations.
@vshymanskyy
Copy link
Author

#4593 - might be relevant.

@cmaglie
Copy link
Member

cmaglie commented Jun 15, 2016

May you post a link to the boards managers packages and the IDE version you're using?

@vshymanskyy
Copy link
Author

vshymanskyy commented Jun 15, 2016 •
edited
Loading

How to reproduce:

  1. Install Arduino IDE v1.6.9
  2. Install MKR1000 board support from the Boards Manager
  3. Check that "Basics->Blink" example compiles fine for MKR1000 board.
  4. Configure additional Boards Manager source: https://redbearlab.github.io/arduino/package_redbear_index.json
  5. Install RedBead Duo package the Boards Manager
  6. "Basics->Blink" example compilation fails for target MKR1000 board.
  7. See in detailed compilation log, that the wrong toolchain is selected.

@facchinm
Copy link
Member

This is probably solved by #4795, would you mind giving the @ArduinoBot build a try?

facchinm added a commit to facchinm/arduino-builder that referenced this issue Jul 4, 2016
@facchinm
Add specifier to generated tool property keys
4652f98 
port of arduino/Arduino#4795 to golang

should solve arduino/Arduino#5042
@facchinm facchinm mentioned this issue Jul 4, 2016
Closed
This was referenced Aug 1, 2016
Merged
Merged
@cmaglie cmaglie added this to the Release 1.6.11 milestone Aug 3, 2016
@per1234 per1234 mentioned this issue Aug 4, 2016
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
Release 1.6.11
Development

Successfully merging a pull request may close this issue.

Fix tools discovery by strictly following json data when available cmaglie/Arduino
3 participants
@cmaglie @vshymanskyy @facchinm