Changes to Build System for Haiku #141
No reviewers
Labels
No labels
3rdparty
Android
API
Author does not respond
bsd
bug
build system/CI
ci-virtual-device
CMake
Contributions Welcome
Core
dependencies
device-specific
documentation
don't_merge
duplicate
enhancement
Example
Haiku
hidraw
hotplug
info required
invalid
libusb
macOS
Misc
Not an issue
question
Release
Test
Test GUI
Windows
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-libusb/hidapi!141
Loading…
Reference in a new issue
No description provided.
Delete branch "haiku"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Relevant issue: #140
This proposal will add support for the Haiku operating system out of the box. A decent bunch of software depends on
hidapialready, and pushing these changes to the upstream version of the codebase would greatly assist with maintainability on our end.The patches were originally written by @CodeforEvolution (although for an older version), hence the commit has been made under their behalf.
@Begasus's tree (which had applied the patches already) was used as a base for this proposal, for the sake of simplicity: https://github.com/Begasus/hidapi/tree/haiku
Please also apply https://github.com/libusb/hidapi/pull/30/commits/b02a43cb2c494960da7520fff668066792371832 to this PR
@ -0,0 +1,39 @@###########################################Please adjust the manual Makefile as in
github.com/libusb/hidapi@51bdec7844Understood.
May I squash the commits?
sure
not sure why do you need to clean right after building it
I don't think that this is relevant to the Haiku issue. Also, I'm not the author of that commit. CC: @z3ntu
I'll give you both write access to my repository for that particular reason, just in case that there's any small changes regarding the CI configurations that need to be addressed.
Here's the invite link that should work for both of you: https://github.com/alwayslivid/hidapi/invitations
Yes this was merged as part of #131 - not sure why it shows up here. I've rebased the branch so it shows up fine now.
@Youw But to answer your question, it's needed because in the second step (
build-manual) the full build should be done so amake cleanis needed in the previous step for the second step to build everything. In addition to that, the build actually fails if not cleaned because of different CFLAGS iircAt least credits should be given to @CodeforEvolution for the initial work on the patch?
@ -109,6 +109,19 @@ case $host inLIBS_LIBUSB_PRIVATE="${LIBS_LIBUSB_PRIVATE} $libusb_LIBS"Needed to detect libiconv_open:
@Begasus I pushed the commit as that person in order to ensure full attribution, so I'm not sure what the problem is?
(I'll check the other changes later)
I've squashed my changes from
b02a43cb2cinto this branch now.Should I move on with including @Begasus's changes? I'm aware that I'm asking way too much, but you know, it's better than having to undo force-pushes.
I've rebased to master and update accordingly (hope force-push wasn't inconvenient
They are already, as far as I can tell
We have a credit in the PR message, and in the commit message. Anything else?
I think we good here
Looks like:
Closes: #30
Wait, I think that credit deserves to go to @Begasus as a co-contributor as well.
np
feel free to commit/ammend/edit message / force-push
No need to give credits to me, @z3ntu did you get a chance to check the changes?
If any issues - reopen/make new PR.
Closes: #140