On Tuesday, June 22, 2010 06:12:38 Tomek CEDRO wrote: > On FreeBSD libusb is rewritten to match BSD license, it is a part of > the system and it use the 0.1 libusb API. Yesterday on Fedora 12 I > have built UrJTAG and as dependency I need to install libftdi that was > already 1.0 using libusb 1.0. On my BSD I have checked if the > libftdi-0.17 program requires linking with the libusb anyway and it > turned true, so it can be difficult to maintain platform independece > and use libftdi-0.x/libusb-0.x and libusb-1.0 at the same time
if you want to keep libusb-0.x support, then use libusb-compat. this provides a wrapper for the 0.x API on top of libusb-1.x. urjtag is sticking to the "real" libusb package (i.e. libusb.org), so the *bsd replacement might need to catch up. or simply use the real libusb package and there isnt a problem. > (also libusb and libusb-win32 have other API???)... no, they really dont > Maybe it is possible to use -lusb for libusb-0.x and -lusb1 for > libusb-1.x? Maybe the libftdi programs should link only with -lftdi > and no -lusb for clear separation from libusb? it wouldnt make a difference because both libraries would be loaded at runtime due to how shared libraries work -mike
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________ UrJTAG-development mailing list UrJTAG-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/urjtag-development
