I'm wondering if this is something in the pipeline?
I've been using the TMC-API for quite some time now with the platformio environment and I like to keep the reference to the full repo tree (for the sake of keeping it up to date) instead of fishing out only the code I need.
However doing it this way platformio always compiles all the files in the lib, needless to say throwing a lot of errors.
I've made a fork where I created a library.json so that using the platformio library manager ( lib_deps = ) I get the desired behavior (see https://github.com/cooked/TMC-API/blob/master/library.json where I included only the files needed to work with the TMC2209)
The approach is not "flexible" yet, more of a proof of concept, so I'm wondering if there's interest in supporting it or someone else is facing similar situation.
I'm wondering if this is something in the pipeline? I've been using the TMC-API for quite some time now with the platformio environment and I like to keep the reference to the full repo tree (for the sake of keeping it up to date) instead of fishing out only the code I need. However doing it this way platformio always compiles all the files in the lib, needless to say throwing a lot of errors.
I've made a fork where I created a library.json so that using the platformio library manager ( lib_deps = ) I get the desired behavior (see https://github.com/cooked/TMC-API/blob/master/library.json where I included only the files needed to work with the TMC2209)
The approach is not "flexible" yet, more of a proof of concept, so I'm wondering if there's interest in supporting it or someone else is facing similar situation.