> Once again, there is a new version of my modular patch. This time, I added a > simple detection of available hardware (comparing /proc/bus/usb/devices and > libfprint/drivers/* files) which appears to work fine in lab condition (I > don't own any of these devices so I had to fool it a little). > > There are some things that could break it, like not using the $driver.c (or > precisely $driver.[any one character]) for the name of the file containing > USB IDs or having restricted access to /proc. > > Fallback is to build all drivers as the device is probably not connected at > the moment
I would be weary of anything that is trying to autodetect hardware at build-time. I'm not against having the option, but I think "--with-drivers=all" would be a more sensible default. The more adventurous can still choose to autodetect things. Besides, if I understand configure.ac correctly, you do not have a "--with-drivers=all" option at all, as not supplying "--with-drivers=..." will default to "--with-drivers=auto" behavior. Am I right? -Artem _______________________________________________ fprint mailing list [email protected] http://lists.reactivated.net/mailman/listinfo/fprint
