Dan Forever
Member
I'm not entirely sure the "headless" options for Teensy are truely headless (CI Woes)
I'm messing around with https://github.com/nektos/act trying to set up some sort of continuous integration for my project with github actions.
The problem is, I seem to be running into problems caused by teensy (I'm hoping once the good Mr. Stoffregen completes arduino cli integration this won't be a problem any more) - specifically in 2 ways:
Is there any way to suppress teeny loader and stop it from being opened automatically by the arduino ide when compiling for teensy?
I'm messing around with https://github.com/nektos/act trying to set up some sort of continuous integration for my project with github actions.
The problem is, I seem to be running into problems caused by teensy (I'm hoping once the good Mr. Stoffregen completes arduino cli integration this won't be a problem any more) - specifically in 2 ways:
- Installing TeensyduinoInstall.linux64, using the `--dir=` command line parameter, I get this error: "error while loading shared libraries: libXft.so.2: cannot open shared object file: No such file or directory" - so I need to install libxft2 first, prior to installing teensyduino. I'm a bit rusty on my Linux knowledge, but I believe this is related to needing a graphical user frontend? It's not a showstopping problem, as I can install the library and work around it, but it's still frustrating.
- However, this problem currently has me stumped - When I compile my project, using the arduino ide and the --verify command line arg, I believe it fails because teensyduino (specifically something called teensy_post_compile) is trying to open teensy-loader. This actually happens locally on my Windows machine too, just day to day use of the arduino IDE, teensy loader opens regardless of whether I clicked verify or upload.
Is there any way to suppress teeny loader and stop it from being opened automatically by the arduino ide when compiling for teensy?