On Mon, 9 Sep 2013, Phil Dibowitz wrote: >>> Yeah, I think at the very least, we should do some sort of transition >>> period. >> >> OK, this adds a new --enable-force-libusb-on-linux option which will use >> libusb but warn. >> >> It also removes the windows bits of libusb since I'm pretty darn sure no one >> has ever used it. And it moves libusbhid.cpp into the top-level libconcord >> directory to prevent the latest version of automake from complaining. >> >> It keeps all the Mac magic, though I haven't tested it with this version of >> the patch yet... > > Oh - and yeah, I haven't updated the docs for this latest version, and I think > there's still some commented stuff out in autoconf/automake. I can do the > final cleanups if you like the approach.
I can't say that I 'like' the approach - I still think hidapi isn't mature enough and doesn't buy us anything on Linux - but I suppose that I can at least live with it. Are you really sure that no one is using the libusb stuff on Windows? We still build it in the solution (not that that means anything) so we'll have to remove it there, too. Why does automake care where files are located? Scott ------------------------------------------------------------------------------ How ServiceNow helps IT people transform IT departments: 1. Consolidate legacy IT systems to a single system of record for IT 2. Standardize and globalize service processes across IT 3. Implement zero-touch automation to replace manual, redundant tasks http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk _______________________________________________ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
