These steps were tested with:
Raspberry Pi 4
Raspbian 10 (buster - Linux 4.19.80-v7l)
VESC Tool V1.25
IMPORTANT NOTE
This throws errors for missing resources due to spaces in res.qrc. If these icons turn out to be an issue, I’ll post updated steps. Long story short, there are a number of icons (resource files) which use spaces rather than underscores and the only solutions is to cleanup the filenames.
That’s it! Within less that 20 minutes on the Raspberry Pi 4 (probably less, I didn’t time it ) you’ll have an executable file in the folder build/lin.
I need to consolidate my steps and will post some instructions once I test them on a clean install of Raspbian. Mostly you need some additional QT libraries.
I also ran into an issue where spaces in the icon filenames caused qmake to fail. I renamed the files (added _) rather than fight the issue. I’m sure there is a way around this, but seeing as how 90% of the resources had properly named files with underscores there really shouldn’t be spaces in filenames.
I actually have also got this working. Was a pretty huge pain in the ass, are you building remotely from a second Linux machine? Setting it up that way was pretty painful.
Think I spent like a day getting remote building setup… Man I’d have to build it so many times to break even on time there . The things we do because we can. I had mine running the mobile version with a little 5" touch display. Pretty fun.
Hey so related I think… I did a thing where I build bldc-tool into a docker image, with some x magic cookie nonsense for the gui. The idea being to be able to run an old version of the tool pretty much anywhere (well x86…). All OS and python/qt dependencies being carried in the image.
Wonder if it’s worth doing some CI thing to try to build a docker image for every release…
Ah I remember. The reason I went to all that trouble was I bought a used complete with vescs running an older firmware. I wanted to grab the settings before upgrading and redoing the setup, and could not find the binary.
I was thinking, if we build every version and send to docker hub, anyone can run any version pretty much on any linux distro, very easily.
Had recently thought about slapping some ci onto the vesc repo since people were complaining about it being hard to get the binaries for different platforms wonder what thought are with Benjamin on this.