Add info to README about libusb 0.1 vs 1.0 and libusb-compat #120
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I wanted those two commits squashed in the pull request. Apparently I still haven't figured out how to do that... |
|
Note that Debian decided NOT to go with libusb-compat, despite wanting to drop libusb-0.1 it's still available as well as libusb-1.0. The reasoning was that the new compat layer was very buggy when introduced so not including it was a big incentive for people to migrate to 1.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Distros with recent versions of libusb (1.x) need to install libusb-compat to provide the legacy (0.1) API expected by mspdebug. After I figured out that libusb-compat was needed, I realized that was what was meant by the mention of libusb-compact on Arch systems (the typo fooled me the first time I read it). Hopefully it's clearer now.