Rubén Lagar wrote: > Now, my question: I am trying to use a U.are.U reader in an embbeded > linux in an ARM architecture. I have tried first to use libdpfp, but I > have seen that that project in discontinued, and that I should use > libfprint instead. But the greater problem with this new library is that > it needs glib and IMAGEMAGICK. > > Could you please help me out, or just give me some information on how to > remove these dependencies? I just want to get a hash from a fingerprint > and try to match it against a local store.
Right now there is no "proper" way of removing those dependencies. In reality you could trivially remove the ImageMagick one by editing the source (only one driver uses that code: aes4000). glib is harder to remove, but you can search the list archives to find a patch which emulates the relevant parts of glib inside libfprint, or alternatively there was another patch which bypassed most of the device detection stuff and eliminated glib that way. In future we'll solve both problems by eliminating the glib dependency, and making the build of each driver optional (this would allow you to exclude aes4000 and hence not need imagemagick) > To install libusb, is it needed any mknod command in the embedded > system, or I just have to copy shared libraries? I don't really > understand how libusb and libfprint work together without any usb driver > module installed in the kernel. libusb is a C interface to the "USB device filesystem" (usbfs) interface offered by the kernel. So, you need usbfs in your kernel, and usbfs mounted at /proc/bus/usb (or udev creating nodes at /dev/bus/usb), and then you need the library itself. Daniel _______________________________________________ fprint mailing list [email protected] http://lists.reactivated.net/mailman/listinfo/fprint
