Skip to content

Sloeber 4.4: expand environment variables in makefile causes different aavr gcc version to be used #1278

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
jantje opened this issue Dec 21, 2020 · 1 comment
Closed

Sloeber 4.4: expand environment variables in makefile causes different aavr gcc version to be used #1278

jantje opened this issue Dec 21, 2020 · 1 comment

Comments

@jantje
Copy link
Member

jantje commented Dec 21, 2020

Creating a project "Talk2 Whisper Node" (used in regression test failing on travis) behaves differently when setting the "expand environment variables in makefile" or not
With expand (default) I get
"C:\eclipse\arduinoPlugin\packages\arduino\tools\avr-gcc\4.8.1-arduino5/bin/avr-g++"
When not expanded I get
"C:\eclipse\arduinoPlugin\packages\arduino\tools\avr-gcc\7.3.0-atmel3.6.1-arduino7/bin/avr-g++

When I delete A.runtime.tools.avr-gcc.path from the workspace settings environmùent variables I go bac to using 7.3 whatever setting

Strangely enough this board is nearly a Arduino avr nano board which does not demonstrate this behaviour

Anyway.. I think the environment variables at the workspace level need to be replaced by a variable provider so I have more control
jantje pushed a commit that referenced this issue Dec 25, 2020
#1268 upgrade 1 config works but build fails due to #1278
e308701
jantje pushed a commit that referenced this issue Dec 26, 2020
#1278 seems to be fixed except for the upgrade scenario
53a057b
@jantje
Copy link
Member Author

jantje commented Dec 31, 2020

This works fine now

@jantje jantje closed this as completed Dec 31, 2020
jantje added a commit that referenced this issue Feb 5, 2021
@jantje
#1278 failed on Linux
1debc34 
Actually it seems like the code to prioritize the arduino provided
platforms never was added
Now I prioritize the latest arduino maintainer platform with
architectures sam samd and avr
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
No milestone
Development

No branches or pull requests
1 participant
@jantje