-
Notifications
You must be signed in to change notification settings - Fork 388
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP: Support for Haiku #30
Conversation
@z3ntu it builds ok here with the patchset, does it fail for you? |
@Youw maybe libiconv should be included in the requirements?
exporting it to the LDFLAGS before build we get:
Any thoughts on this? Using: EDIT this was done in a virtual environment, so the outcome probably is as expected |
I've got your message, but I'll be able to give you a proper answer in a couple of days. |
This wasn't a build failure but a runtime failure I saw on Haiku (using whatever Haiku version was latest in June 2019). I am not 100% sure anymore what exactly happened but I guess I ran my software using hidapi and it failed to open the device or similar - and stepping through with a debugger I got to this |
Thanks for looking into this, if you can find the time to launch your VM try to see if you can update your Haiku install to the latest hrev, that way we won't miss anything that maybe has been fixed in the meantime 👍 |
Thanks! It's not that urgent, getting the patch in I linked should take care of the detection for libiconv, so no need to change anything (at least I don't think so) in the main source |
if by requirements you mean: or is it something else? |
Let's close this in favor of #141 to not split the messages in two different PRs. |
From: https://github.com/haikuports/haikuports/blob/master/dev-libs/hidapi/patches/hidapi-20160919.patchset
I haven't tested this yet, just applied the patch.Fails atlibusb_get_active_config_descriptor
(around line 866 in libusb/hid.c)