How to install on Solus OS?

[knockoutman]

None of the commands work when using with Solus OS, is it supported?

Regards,

[Gibtnix]

Hello,

installing should also be possible, however the dependencies and build steps might be slightly different. I think GCC and make should be the same, only libusb has to be adjusted to the respective distribution's package manager. If it is installed and found by the makefile, compiling should be possible (i.e. downloading the repo's content and just typing 'make' in the respective directory).

If libusb is not found, compiling will result in an error (please post the error message here if so). If compiling works, you can test the binary by calling 'sudo msiklm test' and if this works, you can manually copy it to whatever location you like. Once the binary works, it has no other dependency besides libusb.

[knockoutman]

$ sudo eopkg install gcc make libhidapi-dev
System error. Program terminated.
Repo item libhidapi-dev not found

That's the error, didn't have a chance to use the others. I'm trying to find a solution, Solus OS is great but has some annoying differences.

[knockoutman]

I found a solution for the first step, I used
sudo eopkg install gcc make libusb
Then I tried make and had an error:
fatal error: stdio.h: No such file or directory
#include <stdio.h>
To solve it I used:
sudo eopkg it -c system.devel
I tried make again and got this error:
fatal error: hidapi/hidapi.h: No such file or directory
#include <hidapi/hidapi.h>
I solved the last error with this:
sudo eopkg install hidapi-devel
Then i used make and make clean
Next step was to move the built file to usr/bin (Solus doesn't have the path usr/local/bin):
sudo mv -fv msiklm /usr/bin/msiklm
Then made it executable:
sudo chmod 755 /usr/bin/msiklm
Tested with sudo msiklm test and it says that found a compatible keyboard, so I used:
sudo msiklm red
But didn't work.

[Gibtnix]

Actually it is hard to say what's wrong here. Did you change the IDs in the source code or not? If so then your keyboard might be not compatible. Otherwise I suspect an issue with libusb. You could maybe test with a live ubuntu and verify if it works there and then it might be possible to locate the issue further once it is known that it can bei resolved.