|
Packit Service |
b0a153 |
Notes related to git compilation:
|
|
Packit Service |
b0a153 |
--------------------------------
|
|
Packit Service |
b0a153 |
|
|
Packit Service |
b0a153 |
If you retrieved the libusb repository from git and are using a gcc based
|
|
Packit Service |
b0a153 |
toolchain, be mindful that you should have the autotools installed (autoconf,
|
|
Packit Service |
b0a153 |
automake) and will need to run either ./autogen.sh or ./bootstrap.sh to produce
|
|
Packit Service |
b0a153 |
the configure file.
|
|
Packit Service |
b0a153 |
|
|
Packit Service |
b0a153 |
The difference between autogen.sh and bootstrap.sh is that the former invokes
|
|
Packit Service |
b0a153 |
configure with a default set of options, and will therefore generate a Makefile,
|
|
Packit Service |
b0a153 |
whereas the latter does not invoke configure at all. If using autogen.sh, note
|
|
Packit Service |
b0a153 |
that you can also append options, that will be passed as is to configure.
|
|
Packit Service |
b0a153 |
|
|
Packit Service |
b0a153 |
OS X-specific notes:
|
|
Packit Service |
b0a153 |
-------------------
|
|
Packit Service |
b0a153 |
|
|
Packit Service |
b0a153 |
Starting with Xcode 4.3, neither Xcode.app nor the Xcode 'command line tools'
|
|
Packit Service |
b0a153 |
includes autotools and so running either autogen.sh or bootstrap.sh will result
|
|
Packit Service |
b0a153 |
in the message:
|
|
Packit Service |
b0a153 |
|
|
Packit Service |
b0a153 |
libtoolize or glibtoolize was not found! Please install libtool.
|
|
Packit Service |
b0a153 |
|
|
Packit Service |
b0a153 |
To proceed, you must find and install it from somewhere.
|
|
Packit Service |
b0a153 |
|
|
Packit Service |
b0a153 |
Alternatively, you can use the Xcode project at Xcode/libusb.xcodeproj.
|
|
Packit Service |
b0a153 |
|
|
Packit Service |
b0a153 |
Notes related to submitting new developments:
|
|
Packit Service |
b0a153 |
--------------------------------------------
|
|
Packit Service |
b0a153 |
|
|
Packit Service |
b0a153 |
If you submit a new development to libusb (eg: new backend), that is unlikely
|
|
Packit Service |
b0a153 |
to fit in a couple of small patches, we would kindly suggest that you create a
|
|
Packit Service |
b0a153 |
public account on github, if you don't have one already, and then fork a new
|
|
Packit Service |
b0a153 |
libusb repository under this account from https://github.com/libusb/libusb.
|
|
Packit Service |
b0a153 |
|
|
Packit Service |
b0a153 |
Then you can create a git branch for your work, that we will be able to better
|
|
Packit Service |
b0a153 |
reference and test.
|
|
Packit Service |
b0a153 |
|
|
Packit Service |
b0a153 |
We also suggest that, if you are planning to bring in a large development, you
|
|
Packit Service |
b0a153 |
try to involve the libusb community early by letting the mailing list know, as
|
|
Packit Service |
b0a153 |
you may find that other people might be eager to help you out.
|
|
Packit Service |
b0a153 |
See http://mailing-list.libusb.info for details on how to join the mailing list.
|