libusb-1.0 + libftdi-0.18 works for me without async support. as such, ive cleaned up the configure logic: - detect libusb-1.0 via pkg-config - detect libusb-0.1 via pkg-config - do not perform any link tests against libusb - do not abort if libftdi lacks async support and we have libusb-1.0
i think this should address your issues implicitly by preferring libusb-1.0 over libusb-0.1 which is provided by the libusb-compat layer i dropped the libusb link tests as they break when using latest libusb-winusb from upstream which now supports dll building and as such, builds the public api with stdcall. so the symbols dont match what a simple link test expects. -mike
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________ UrJTAG-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/urjtag-development
