Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(1038)

Unified Diff: third_party/libusb/src/README.git

Issue 19713005: Update libusb 1.0.9 to libusbx 1.0.16 (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: Created 7 years, 5 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: third_party/libusb/src/README.git
diff --git a/third_party/libusb/src/README.git b/third_party/libusb/src/README.git
new file mode 100644
index 0000000000000000000000000000000000000000..6d7db42a1851825d62269d301cf4981cb4f95281
--- /dev/null
+++ b/third_party/libusb/src/README.git
@@ -0,0 +1,29 @@
+Notes related to git compilation:
+--------------------------------
+
+If you retrieved the libusbx 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.
+
+The difference between autogen.sh and bootstrap.sh is that the former invokes
+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.
+
+
+Notes related to submitting new developments:
+--------------------------------------------
+
+If you submit a new development to libusbx (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.
+
+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
+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.

Powered by Google App Engine
This is Rietveld 408576698