X-Git-Url: http://review.tizen.org/git/?a=blobdiff_plain;f=README.git;h=eab938cb2d92284f9ffe88ac2c443dc5ed3502ad;hb=31ff09c35a582cc6870dfd2c9924d62e79d2f933;hp=6d7db42a1851825d62269d301cf4981cb4f95281;hpb=4e1d77d3c4a370f2b2d87f396859a5e249473dbf;p=platform%2Fupstream%2Flibusb.git

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