A while ago I forked Paul’s core to add a new USB type that emulates a particular legacy joystick. It works well, but for reasons relating to the host USB stack, it cannot use USB serial. That’s fine - when I’ve needed to debug, I can use the hardware UARTs.
But when other people try to build they run into trouble as teensyduino continues to grow and develop, because other code outside the core - eg the antplus library - expects Serial.printf etc to be defined. I can give them a patch, but eventually it breaks again when something else changes. Is there a canonical way to tell the entire system that I want it to stay away from serial interface zero, or should I see if I can create my own do-nothing functions for this in the core? Thanks!
But when other people try to build they run into trouble as teensyduino continues to grow and develop, because other code outside the core - eg the antplus library - expects Serial.printf etc to be defined. I can give them a patch, but eventually it breaks again when something else changes. Is there a canonical way to tell the entire system that I want it to stay away from serial interface zero, or should I see if I can create my own do-nothing functions for this in the core? Thanks!
