Closed LRYMND closed 2 years ago
Are you running on buster or bullseye? also 32 bit or 64 bit?
Upgrading is possible, but v2 of the usb protocol uses a different api so would need quite a bit of work.
Running Bullseye and tried on 32bit and 64bit.
Ok, I don’t think you are actually seeing an error here, those logs look like prebuilt binaries logs. It should just build from source, which as you said you get an appimage I guess it is working fine.
The no directory error perhaps sounds like a permissions issue? Try and run the setup-pi script in the repo, this creates udev rules that allow you to remove the sudo command when running.
Apparently it's unable to set some permissions:
Creating udev rules
SUBSYSTEM=="usb", ATTR{idVendor}=="1314", ATTR{idProduct}=="1520", MODE="0660", GROUP="plugdev"
setup-pi.sh: 12: [[: not found
-e Unable to create permissions
The file for the new rules is created however and I ran the shell with sudo.
And how about if you now run your built appimage without sudo and sandbox option?
If it’s still no luck I will image a fresh pi in 32bit bullseye, all my testing so far was on buster
I tried rebuilding once more just to be sure but it's still printing "No such file or directory" when trying to execute. I will do the same and install buster on another SD Card to see if that's really the issue.
Build on Buster was successful and is running. Having some other issues now that I need to investigate but the AppImage launches. Thanks for the poke into the right direction!
When trying to build the app it is having troubles to do the pre build for the node usb module.
Here's the log:
So even though I get an appimage at the end, when trying to launch it (after chmod +x) it only says "no such file or directory"
Libudev is installed. When trying to build the "node usb electron test app" which is using the latest node usb release it doesn't throw this error and builds successfully.
Is it maybe an issue with 1.7.2? I tried to pin the dependency on 1.7.1 but it's always going for 1.7.2.
Is it eventually possible to upgrade to the latest node usb release and see if that resolves the issue?