Google Git
Sign in
flutter / third_party / libusb / a96937af9935c569b679d8ada2f59e90754b700a
commita96937af9935c569b679d8ada2f59e90754b700a[log] [tgz]
authorChris Dickens <christopher.a.dickens@gmail.com>Sun Jan 26 14:29:48 2020 -0800
committerChris Dickens <christopher.a.dickens@gmail.com>Sun Jan 26 14:29:48 2020 -0800
tree4d01a888c8d5da48a7c890ca084be7fbdd3eed3f
parent48200f2cc23633899270e7c666ac7e948ead8df1 [diff]
autobuild: Fix two issues

The test for defining the automake conditional for the poll
implementation was keying off of the threads variable, producing
incorrect results for Cygwin.

A simple typo in the Makefile causes a build failure when
cross-compiling for Windows.

Signed-off-by: Chris Dickens <christopher.a.dickens@gmail.com>
3 files changed
tree: 4d01a888c8d5da48a7c890ca084be7fbdd3eed3f
  1. .private/
  2. android/
  3. doc/
  4. examples/
  5. libusb/
  6. msvc/
  7. tests/
  8. Xcode/
  9. README ⇨ README.md
  10. .gitattributes
  11. .gitignore
  12. .travis.yml
  13. appveyor.yml
  14. appveyor_cygwin.bat
  15. appveyor_minGW.bat
  16. AUTHORS
  17. autogen.sh
  18. bootstrap.sh
  19. Brewfile
  20. ChangeLog
  21. configure.ac
  22. COPYING
  23. INSTALL_WIN.txt
  24. libusb-1.0.pc.in
  25. Makefile.am
  26. NEWS
  27. PORTING
  28. README.git
  29. README.md
  30. TODO
  31. travis-autogen.sh
README.md

libusb

Build Status Build status Coverity Scan Build Status

libusb is a library for USB device access from Linux, macOS, Windows, OpenBSD/NetBSD and Haiku userspace. It is written in C (Haiku backend in C++) and licensed under the GNU Lesser General Public License version 2.1 or, at your option, any later version (see COPYING).

libusb is abstracted internally in such a way that it can hopefully be ported to other operating systems. Please see the PORTING file for more information.

libusb homepage: http://libusb.info/

Developers will wish to consult the API documentation: http://api.libusb.info

Use the mailing list for questions, comments, etc: http://mailing-list.libusb.info

(Please use the mailing list rather than mailing developers directly)