On Thu, Jun 18, 2009 at 07:34:36PM +0100, Bastien Nocera wrote: > I would urge you to use fprintd instead of libfprint directly (and you'd > get the Python bindings for free).
Sounds like a good idea. I am trying to compile 4ea1c48 and getting the following error. Do I need a newer version of something? libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wall -Wmissing-prototypes -I/usr/include/libfprint -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/PolicyKit -DLOCALEDIR=\"/usr/share/locale\" -DPLUGINDIR=\"/usr/lib/fprintd/modules\" -g -O2 -MT device.lo -MD -MP -MF .deps/device.Tpo -c device.c -fPIC -DPIC -o .libs/device.o device.c: In function ‘fprint_device_get_property’: device.c:197: warning: implicit declaration of function ‘fp_driver_get_scan_type’ device.c:197: error: ‘FP_SCAN_TYPE_PRESS’ undeclared (first use in this function) device.c:197: error: (Each undeclared identifier is reported only once device.c:197: error: for each function it appears in.) _______________________________________________ fprint mailing list [email protected] http://lists.reactivated.net/mailman/listinfo/fprint
