| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
Building libusb from another build directory doesn't properly work right
now, as calling autogen.sh from there won't work.
An example is when using jhbuild to build it.
So always use absolute paths to call configure and bootstrap scripts
Signed-off-by: Ludovic Rousseau <ludovic.rousseau@free.fr>
|
| |
|
|
| |
Signed-off-by: Chris Dickens <christopher.a.dickens@gmail.com>
|
| |
|
|
| |
Signed-off-by: Nathan Hjelm <hjelmn@me.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
See http://people.gnome.org/~walters/docs/build-api.txt
Hdg: I know this may seem unnecessary since we also have bootstrap.sh, but
the Gnome people are doing continues build testing of Gnome + dependencies
and having all autogen.sh scripts support NOCONFIGURE=1 makes live easier for
them. Note that in return we get "free" continues build-testing and patches
and / or a heads up when we break things.
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
|
| |
|
|
|
| |
See https://github.com/tobygray/libusbx/tree/testing as well
as http://libusbx.1081486.n5.nabble.com/Libusbx-devel-Crashes-tt433.html#a438
|
| |
|
|
| |
* "$@" will correctly handle arguments with spaces
|
| |
|
|
| |
* The script will not continue if something fails (like a command not found)
|
| |
|
|
|
|
| |
* Script is valid for bash but not any /bin/sh
* Thanks to Xiaofan Chen for the bug report
http://sourceforge.net/mailarchive/message.php?msg_id=29217871
|
| |
|
|
|
| |
bootstrap.sh does not invoke configure whereas autogen.sh does.
This allows libusbx users to choose the one that suits them best.
|
| | |
|
| |
|
|
|
|
|
| |
This helps on Mac OS X where an old glibtoolize is included in the
system and newer, manually installed, versions provide libtoolize.
See also http://marc.info/?m=132490560131894
|
| | |
|
|
|
Basic library structure which supports enumerating detected USB devices
|
