summaryrefslogtreecommitdiff
path: root/configure.ac
AgeCommit message (Collapse)AuthorFilesLines
2012-09-25Rename libusbredirparser.pc to libusbredirparser-0.5.pcusbredir-0.5.2Hans de Goede1-2/+2
The usbredir 0.5 release introduced the new API for 64 bit packet ids, but it kept the libusbredirparser.pc name as is, meaning that older versions of qemu will still have their pkg-config check for usbredirparser fulfilled, and build with the usb-redir device. Due to the API change there will be some compiler warnings, but the build will succeed, however the usb-redir device will be broken on 32 bit machines. To solve this, this patch renames the libusbredirparser.pc file to libusbredirparser-0.5.pc, so that it will no longer fulfill the pkg-config check of the qemu-1.2 and older releases, stopping the (silent) breakage. A patch has been send to qemu-devel to adjusts qemu master's configure. Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2012-09-25Prepare for a 0.5.1 releaseusbredir-0.5.1Hans de Goede1-1/+1
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2012-08-31usbredirparser: Update API for 64 bit packet idsHans de Goede1-2/+2
-ABI and API breakage !! -Bump libusbredirparser soname version -Change version to 0.5 so that libusbredirparser users can test for the new API Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2012-05-23configure: Windows: ignore usbredirserver and usbredirtestclient subdirsUri Lublin1-0/+13
Their build fails, so skip them. Things to fix to make the them work on Win32 include sockets, signals, threads and more.
2012-04-02Release 0.4.3usbredir-0.4.3Hans de Goede1-1/+1
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2012-03-06Release 0.4.2usbredir-0.4.2Hans de Goede1-1/+1
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2012-02-25Release usbredir-0.4.1usbredir-0.4.1Hans de Goede1-1/+1
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2012-02-25Compile with -Wall -Werror by default and fix existing warningsHans de Goede1-0/+15
The direct trigger for making this change is the fact that the 0.4 release is broken due to a return without a value in a non void function. Somehow this happened to always do the right thing in my testing, but not for others. This is something which should have been caught by a compiler warning, but I always build from git, and then no -Wall (let alone -Werror) gets passed to the compiler, which allowed this to slip through. So to avoid future embarrassment this patch changes the configure script to add various compiler options to CFLAGS by default, which should catch most detectable mistakes. Note that this change modifies CFLAGS directly, so if you're somehow specifying your own CFLAGS nothing will change (this is intentional). Also all added flags are checked, so if you've a compiler which is not gcc nothing will change. This patch also fixes the few warnings actually present in the code, so as to not have a state in the commit tree where the code does not compile. Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2012-02-22Release 0.4usbredir-0.4Hans de Goede1-1/+1
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2012-02-10Add an usb_redir_device_reject packetHans de Goede1-1/+1
Add an usb_redir_device_reject packet to allow notifying the usb-host when an usb-guest rejects a device because of usb-guest side device filtering. Also bump the version to 0.3.4 so that apps can check if libusbredirparser / libusbredirhost knows about usb_redir_device_reject by checking the version number. Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2012-01-11usbredirparser: Add usbredirfilter codeHans de Goede1-1/+1
Add usbredirfilter code, to help apps exclude certain devices from redirection. See the new usbredirfilter.h for details. This commit also bumps the reported version to 0.3.3, so that apps using libusbredirparser can check for this version to check the presence of the new usbredirfilter functions. Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2011-12-19Allow specifying locking functions for multi-threading on open / createHans de Goede1-1/+1
Having separate set_locking_funcs functions causes the locking functions to be available potentially too late. And it just is not very pretty. This commit changes the API (in a way which is backward compat with 0.3.1), so that locking functions can be specified at creation time, just like all the other callbacks. This commit also bumps the reported version to 0.3.2, so that apps using libusbredirhost can check for this version to check the presence of the new usbredirhost_open_full function. Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2011-11-25Switch to autotools build systemChristophe Fergeau1-0/+41
Replace the current build system with an autotools based one. HdG, 3 small changes: 1) LIBUSBREDIRPARSER_SO_VERSION 1:0:0 should be 0:0:0, so that the soname does not change by going from Makefiles to autofoo 2) Drop LIBGPOD_SO_VERSION from configure.ac 3) Make libusb pkgconfig check require version >= 1.0.9 Signed-off-by: Hans de Goede <hdegoede@redhat.com>