diff options
-rw-r--r-- | README.git | 30 | ||||
-rw-r--r-- | libusb/version_nano.h | 2 |
2 files changed, 31 insertions, 1 deletions
diff --git a/README.git b/README.git new file mode 100644 index 0000000..95debb1 --- /dev/null +++ b/README.git @@ -0,0 +1,30 @@ +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 +libsubx 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 https://lists.sourceforge.net/lists/listinfo/libusbx-devel for details on +how to join the mailing list.
\ No newline at end of file diff --git a/libusb/version_nano.h b/libusb/version_nano.h index ec7e590..17b4a2f 100644 --- a/libusb/version_nano.h +++ b/libusb/version_nano.h @@ -1 +1 @@ -#define LIBUSB_NANO 10541 +#define LIBUSB_NANO 10542 |