Ihor Dutchak
Ihor Dutchak
So yes, we do hit some limitation here (e.g. cannot re-use CMake alias targets), but there is a straight-forward workaround and so far I came up with this: https://github.com/libusb/hidapi/tree/meson_support I...
@eli-schwartz your comments on https://github.com/libusb/hidapi/tree/meson_support are welcome
Lets make it even better: https://github.com/libusb/hidapi/pull/410
> move the hidapi source tree into subprojects/hidapi_build_cmake/ That shouldn't be required. Can you share failure logs when running on the original branch?
Ah, I see: ``` hidapi_build_cmake| WARNING: CMake: path C:/projects/hidapi/hidapi is inside the root project but not inside the subproject. hidapi_build_cmake| WARNING: --> Ignoring. This can lead to build errors. hidapi_build_cmake|...
Updated the implementation. Added CI scripts.
https://qbicz.github.io/hidapi/ looks fine to me. Way better than nothing. Will we be able to replace it later with some separate page (without modifying a README)? (README is great but not...
- hidraw: once we have [`hid_get_path`](https://github.com/libusb/hidapi/pull/164) I believe it is enough to identify the physysical device, since paths like `/dev/hidraw*` are [easily mapped](https://arvchristos.github.io/post/matching-dev-hidraw-devices-with-physical-devices/) to `/sys/class/hidraw/hidraw*`; that information should be more...
Resolved by #432
Good catch. Agree, it should be handled properly. The fact is - I don't believe this functionality needed at all for device to function. I'll clean it up next time...