Raspberry Pi support

[mterencelao]

Builds for ARM64 boards are much appreciated. I've put together a portable computer using Raspberry Pi and happen to own a Pokit Pro. Having this running on my Raspberry Pi would help reduce my dependence on phones.

[pcolby]

Hi @mterencelao, have you tried it? I don't have access to RPi at the moment, but I would expect it the build and run okay, as long as the RPi's Bluetooth adapter is compatible with Bluez.

If you get a chance to try it, let us know how it goes. If you run into any issues, let us know, and I might be able to help 😄

[mterencelao]

Are you able to specify which Qt libraries are needed to build from source? I'm running Arch Linux ARM.

[pcolby]

I'm not sure about Arch, but as an example, this is the full set of packages you'd want for Ubuntu's Qt5:

qtbase5-dev qtbase5-doc-dev qtconnectivity5-dev qtconnectivity5-doc-html qttools5-dev qttools5-dev-tools

Or for Qt6:

qt6-base-dev qt6-base-dev-tools qt6-connectivity-dev qt6-l10n-tools qt6-tools-dev qt6-tools-dev-tools

Additionally:

• for code coverage reporting: lcov
• for documentation: doxygen

Cheers.

[mterencelao]

It builds and runs successfully! But my files are all over the place. I'll have to find a suitable external storage before I attempt again. But first test got me this result:

$ ./dokit status
qt.bluetooth.bluez: Missing CAP_NET_ADMIN permission. Cannot determine whether a found address is of random or public type.
dokit.cli.command: Looking for first available Pokit device...
Device name:           PokitPro
Firmware version:      2.0
Maximum voltage:       850
Maximum current:       10
Maximum resistance:    3000
Maximum sampling rate: 1000
Sampling buffer size:  16384
Capability mask:       0
MAC address:           84:FD:27:86:DA:08
Device status:         Idle (0)
Battery voltage:       4.103
Battery status:        Good (1)
Switch position:       Voltage (0)
Charging status:       Discharging (0)

[mterencelao]

How do you install this, by the way? Or is there no such thing as installing?

[pcolby]

There's currently no official installer. It you have linuxdeploy installed, then you can run: make cli-appimage to build an AppImage that you can deploy to other Linux machines.

What kind of install options would you be interested in? make install? A *.deb? etc? (Just curious / gauging interest 🙂)

[mterencelao]

What kind of install options would you be interested in? make install? A *.deb? etc? (Just curious / gauging interest 🙂)

Apologies for the long wait. I'm currently running Arch Linux ARM on a Raspberry Pi. (I tested your app on Windows and Arch Linux ARM, by the way.) I'm not one to ask for a specific packaged format, but I suppose packaging it to .deb is a good idea. AppImage is awesome, too.

There's currently no official installer. It you have linuxdeploy installed, then you can run: make cli-appimage to build an AppImage that you can deploy to other Linux machines.

And linuxdeploy? That sounds like using an Android phone to create an executable. (Edit: I was looking at the wrong project. I take it that this is what you mean.) I guess I'll just try out the make cli-appimage.

[pcolby]

Apologies for the long wait.

No need to apologise ☺️

I take it that this is what you mean.

Yep, that's the one. You'll also need to the Qt plugin for it too. I just download the latest .AppImage files from these repos, and drop them into a folder into the bin path:

• https://github.com/linuxdeploy/linuxdeploy/releases
• https://github.com/linuxdeploy/linuxdeploy-plugin-appimage/releases
• https://github.com/linuxdeploy/linuxdeploy-plugin-qt/releases

I'll have a look at creating .deb file... (I've created RPMs for work a lifetime ago, but never got to debs)

[mterencelao]

I have finished testing your ARM binary, and it worked wonderfully.

I have also just composed a PKGBUILD (Arch Linux installer script) for you here, but I leave it you to decide whether or not to include this to your project. Arch Linux would much prefer building against the zipped source file, and I may work on a version to meet that as well. But I stop short of maintaining the script, as I am not sure I can commit to it.

UPDATE: The same link now also contains the PKGBUILD for the preferred source code version. (Labeled as "PKGBUILD.2". The original one is "PKGBUILD.1".) It should not take much to make a Git-based version from that now.