Think we all have been there. As you said goes easier on the second round. Good luck with the updates
Who me?
Paul - Definitely been there
All - semi random
Was playing around some with Linux box and was wondering if I could setup like when I am working on some of the Robotis boards like OpenCM or OpenCR, where I have their boards listing under tools->boards twice, one for the current release and another time for the DEV branch... (they work a little different in that their master/main branch is the current released code, and the dev branch is the WIP.
So I hacked up a setup, where I created the directory ~/Arduino/hardware/teensy_189
And then I created a symbolic link to the stuff I am building using arduino 1.8.9, the directory I created: ln -s ~arduino-1.8.19/hardware/teensy/avr
Then they both show up in the tools hardware menu:
However the build won't work...
Code:
Compilation error: fork/exec /home/kurte/Arduino/hardware/teensy_189/../tools/arm/bin/arm-none-eabi-g++: no such file or directory
The problem is the system can not find the build tools as the platform.txt is setup to hard coded ../tools ...
Paul, I know you already know this as you updated the platform.txt for the arduino cli install to handle this:
Code:
# Teensyduino Installer
#compiler.path={runtime.hardware.path}/../tools/
#teensytools.path={runtime.hardware.path}/../tools/
# Arduino Boards Manager
compiler.path={runtime.tools.teensy-compile.path}/
teensytools.path={runtime.tools.teensy-tools.path}/
By changing the platform.txt to not use the relative names, but instead where the tools are installed in the ~/.arduino/packages/teensy
Again I know this is premature, but looks like this type of an approach could work....