-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fatal error: gio/gio.h: No such file or directory #6
Comments
@dkibet, thanks for reporting the error. I will check it soon. |
Libfprint version 1.90.1 is de facto beta 2.0. In other words, the old library API is broken and the wrapper must be completely rewritten. This may take a couple of weeks. |
I kind of need it but I'd be happy to wait. Thank you PS: is it possible to save the prints to a db instead? |
I just tried with libfprint-V_1_90_0 but i am still getting the same error. 0_99_0 worked, thanks! |
After some investigation, I figure out that this wrapper not needed at all for libfprint v2.0 See example from official repo: https://gitlab.freedesktop.org/libfprint/libfprint/-/blob/master/tests/capture.py |
Hey, Sorry i had to take a break from this project, decided to pick it up again. Those examples work great, Thanks! I am missing one feature though, verification. I can't seem to find documentation anywhere, if you know any more information about it I'd really appreciate it. |
If you use this wrapper and LibFprint v0.99.0, you can use examples/verify.py If you use GLib introspection and LibFprint v2 (1.90.1), then you can explore https://gitlab.freedesktop.org/libfprint/libfprint/-/blob/master/examples/verify.c (I assume you understand C-lang) . Then, using GLib introspection, you can reproduce the example from You can also request a python verification example in the official LibFprint repository: https://gitlab.freedesktop.org/libfprint/libfprint/-/issues |
This is the complete error message when trying to install.
I am using:
python 3.8.2
archlinux
Cython version 0.29.16
libfprint 1.90.1-1
glibc 2.31-2
The text was updated successfully, but these errors were encountered: