marcmerlin
Well-known member
Howdy,
https://www.pjrc.com/teensy/td_download.html says
" Teensyduino can automatically install many libraries that are tested and verified to work with Teensy. Usually it's best to allow the installer to add them all."
Let's say I let it install its own copy of FastLED. Why would I do this if I'm working on other chips too and I have FastLED in my ~/arduino/libraries?
Now that arduino IDE has a libraries manager, why would I want to muddle the waters and have yet another copy (maybe out of date) of libraries in hardware/teensy/avr/libraries ?
I understand that teensy used to have patched version of standard libraries, but I'm assuming that those patches are now merged upstream, are they not?
How do I easily know if some of those libraries differ from upstream and whether I'd want to use that forked copy over the standard copy?
Thanks, Marc
https://www.pjrc.com/teensy/td_download.html says
" Teensyduino can automatically install many libraries that are tested and verified to work with Teensy. Usually it's best to allow the installer to add them all."
Let's say I let it install its own copy of FastLED. Why would I do this if I'm working on other chips too and I have FastLED in my ~/arduino/libraries?
Now that arduino IDE has a libraries manager, why would I want to muddle the waters and have yet another copy (maybe out of date) of libraries in hardware/teensy/avr/libraries ?
I understand that teensy used to have patched version of standard libraries, but I'm assuming that those patches are now merged upstream, are they not?
How do I easily know if some of those libraries differ from upstream and whether I'd want to use that forked copy over the standard copy?
Thanks, Marc