• Home
Name Date Size #Lines LOC

..--

.private/12-May-2024-284187

Xcode/12-May-2024-1,5681,507

android/12-May-2024-476222

darwin/12-May-2024-16134

doc/12-May-2024-2,5161,947

examples/12-May-2024-3,8432,875

libusb/12-May-2024-30,85719,281

linux/12-May-2024-17742

msvc/12-May-2024-8,7338,087

tests/12-May-2024-437264

windows/12-May-2024-16229

.gitattributesD12-May-2024179 87

.gitignoreD12-May-2024721 6968

.travis.ymlD12-May-20241.4 KiB6054

AUTHORSD12-May-20242.9 KiB170168

BUILD.gnD12-May-20242.9 KiB110102

BrewfileD12-May-202457 54

COPYINGD12-May-202425.8 KiB505418

ChangeLogD12-May-202412.8 KiB308271

INSTALL_WIN.txtD12-May-20241.7 KiB5239

Makefile.amD12-May-20241.4 KiB5136

NEWSD12-May-202493 32

OAT.xmlD12-May-20245.1 KiB8327

PORTINGD12-May-20243.8 KiB9566

READMED12-May-20241.3 KiB3324

README.OpenSourceD12-May-2024267 1110

README.gitD12-May-20241.8 KiB4230

README.mdD12-May-20241.3 KiB3324

TODOD12-May-2024126 32

appveyor.ymlD12-May-20242 KiB7367

autogen.shD12-May-2024139 95

bootstrap.shD12-May-202477 95

bundle.jsonD12-May-2024744 3131

configure.acD12-May-202413.7 KiB386357

libusb-1.0.pc.inD12-May-2024312 1210

testD12-May-20240

README

1# libusb
2
3[![Build Status](https://travis-ci.org/libusb/libusb.svg?branch=master)](https://travis-ci.org/libusb/libusb)
4[![Build Status](https://ci.appveyor.com/api/projects/status/xvrfam94jii4a6lw?svg=true)](https://ci.appveyor.com/project/LudovicRousseau/libusb)
5[![Coverity Scan Build Status](https://scan.coverity.com/projects/2180/badge.svg)](https://scan.coverity.com/projects/libusb-libusb)
6
7libusb is a library for USB device access from Linux, macOS,
8Windows, OpenBSD/NetBSD, Haiku and Solaris userspace.
9It is written in C (Haiku backend in C++) and licensed under the GNU
10Lesser General Public License version 2.1 or, at your option, any later
11version (see [COPYING](COPYING)).
12
13libusb is abstracted internally in such a way that it can hopefully
14be ported to other operating systems. Please see the [PORTING](PORTING)
15file for more information.
16
17libusb homepage:
18http://libusb.info/
19
20Developers will wish to consult the API documentation:
21http://api.libusb.info
22
23Use the mailing list for questions, comments, etc:
24http://mailing-list.libusb.info
25
26- Hans de Goede <hdegoede@redhat.com>
27- Xiaofan Chen <xiaofanc@gmail.com>
28- Ludovic Rousseau <ludovic.rousseau@gmail.com>
29- Nathan Hjelm <hjelmn@cs.unm.edu>
30- Chris Dickens <christopher.a.dickens@gmail.com>
31
32(Please use the mailing list rather than mailing developers directly)
33

README.OpenSource

1[
2  {
3    "Name": "libusb",
4    "License": "LGPL V2.1",
5    "License File": "COPYING",
6    "Version Number": "1.0.24",
7    "Upstream URL": "https://libusb.info/",
8    "Description": "libusb is a C library that provides generic access to USB devices."
9  }
10]
11

README.git

1Notes related to git compilation:
2--------------------------------
3
4If you retrieved the libusb repository from git and are using a gcc based
5toolchain, be mindful that you should have the autotools installed (autoconf,
6automake) and will need to run either ./autogen.sh or ./bootstrap.sh to produce
7the configure file.
8
9The difference between autogen.sh and bootstrap.sh is that the former invokes
10configure with a default set of options, and will therefore generate a Makefile,
11whereas the latter does not invoke configure at all. If using autogen.sh, note
12that you can also append options, that will be passed as is to configure.
13
14OS X-specific notes:
15-------------------
16
17Starting with Xcode 4.3, neither Xcode.app nor the Xcode 'command line tools'
18includes autotools and so running either autogen.sh or bootstrap.sh will result
19in the message:
20
21libtoolize or glibtoolize was not found! Please install libtool.
22
23To proceed, you must find and install it from somewhere.
24
25Alternatively, you can use the Xcode project at Xcode/libusb.xcodeproj.
26
27Notes related to submitting new developments:
28--------------------------------------------
29
30If you submit a new development to libusb (eg: new backend), that is unlikely
31to fit in a couple of small patches, we would kindly suggest that you create a
32public account on github, if you don't have one already, and then fork a new
33libusb repository under this account from https://github.com/libusb/libusb.
34
35Then you can create a git branch for your work, that we will be able to better
36reference and test.
37
38We also suggest that, if you are planning to bring in a large development, you
39try to involve the libusb community early by letting the mailing list know, as
40you may find that other people might be eager to help you out.
41See http://mailing-list.libusb.info for details on how to join the mailing list.
42

README.md

1# libusb
2
3[![Build Status](https://travis-ci.org/libusb/libusb.svg?branch=master)](https://travis-ci.org/libusb/libusb)
4[![Build Status](https://ci.appveyor.com/api/projects/status/xvrfam94jii4a6lw?svg=true)](https://ci.appveyor.com/project/LudovicRousseau/libusb)
5[![Coverity Scan Build Status](https://scan.coverity.com/projects/2180/badge.svg)](https://scan.coverity.com/projects/libusb-libusb)
6
7libusb is a library for USB device access from Linux, macOS,
8Windows, OpenBSD/NetBSD, Haiku and Solaris userspace.
9It is written in C (Haiku backend in C++) and licensed under the GNU
10Lesser General Public License version 2.1 or, at your option, any later
11version (see [COPYING](COPYING)).
12
13libusb is abstracted internally in such a way that it can hopefully
14be ported to other operating systems. Please see the [PORTING](PORTING)
15file for more information.
16
17libusb homepage:
18http://libusb.info/
19
20Developers will wish to consult the API documentation:
21http://api.libusb.info
22
23Use the mailing list for questions, comments, etc:
24http://mailing-list.libusb.info
25
26- Hans de Goede <hdegoede@redhat.com>
27- Xiaofan Chen <xiaofanc@gmail.com>
28- Ludovic Rousseau <ludovic.rousseau@gmail.com>
29- Nathan Hjelm <hjelmn@cs.unm.edu>
30- Chris Dickens <christopher.a.dickens@gmail.com>
31
32(Please use the mailing list rather than mailing developers directly)
33