libusb-1.0.so.0 is a symlink to the so, you can just create it :
ln -s libusb-1.0.so libusb-1.0.so.0
After 30 years developing enterprise applications and consulting to fortune 500 organisations across the globe, i was lucky enough to be able to sell my company and retire. These days I prefer to get back to the nuts and bolts of building things from scratch. I no longer have to worry about the frustration giving me gray hairs, because I'm already gray :)
I love learning new things and being part of a community of mutual respect and collaboration. Being the dumbest guy in the room is invigorating because there is so much opportunity to learn.
@mawg depending on the complexity of your code I find remote logging is simpler, for reasons I explained above. @JP-Norair has a different view and I don't entirey disagree with him, but sometimes the simpler solution is a better fit. You'll need to make your own judgement as to what fits you best.
@El-Berto Just look down your inlcude path for the header files and then examine their content.
You may find it easier to use an IDE to do your work, I use Netbeans 11 on Ubuntu 18, it will assist you by flagging errors and allowing you to open any of the files you may be referring to in your code. You could use eclipse also, but I don't fine it works as well with this compiler.
It looks like it is set to target-mipsel_24kc_musl-1.1.16 which won't exist so your include of ugpio/ugpio.h will not resolve.
Looks like your connection to Community was lost, please wait while we try to reconnect.