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.