Override complete compiler tool paths for chipKIT. #159
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously we were setting the AVR tools path to the PIC32 tools path because it
made grabbing the compiling tools easier. Consequently, it made finding the
avrdude path much harder, especially since the avrdude files are in different
locations in the Linux distributions of MPIDE and Arduino.
Instead, we set the AVR tools path to the correct path (where AVR dude
lives), and totally override the CC, CXX, etc. paths to point to their PIC32
equivalents.
Eventually this will probably get merged with whatever changes made to handle the multiple platforms supported by Arduino 1.5 (AVR and ARM). The flashing tool and compiling tools are conflated in the current release, but we may need to split it up going forward based on this example (i.e. the chipKIT uses pic32 tools but still uses avrdude to flash).