On 2019-12-16 14:27, Brendan Horan wrote:
----- On 16 Dec, 2019, at 10:16 PM, Anton Lundin glance@acc.umu.se wrote:
So, the real error we hit here is that LIBUSB_ERROR_BUSY . We try to open the device but we get a error as answer.
Why does subsurface get a LIBUSB_ERROR_BUSY, when dctool can open the device just fine, thats the question.
The appimages libdivecomputer is build directly against libusb, is your local build against hidapi ?
You can check with `grep -i hid config.h` in your libdivecomputer build tree.
Now this gets interesting. I think I am using libusb :
/t/libdivecomputer (master|…) $ grep -i hid config.h /* hidapi library */ /* #undef HAVE_HIDAPI */ /t/libdivecomputer (master|…) $ grep -i usb config.h /* libusb library */ #define HAVE_LIBUSB 1
That's normal. On Linux, libusb is currently the default because hidapi is just a wrapper around libusb.
Jef