My ultimate goal: use the fingeprint reader of a Lenovo T430 on Ubuntustdio 20.04.
Type oft the device, according to lsusb
:
Bus 001 Device 003: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF advanced mode).
According to https://fprint.freedesktop.org/supported-devices.html they support this device.
I downloaded libfprint-master.tar.gz using the button Download from https://gitlab.freedesktop.org/libfprint/libfprint.git and unzipped it to some directory libfprintf
. After unzipping, I find another directory libfprint-master
in it and there is among others a directory builddir
in that one.
After installing python and meson-0.61.1, I also added
export PATH="$PATH:/home/verwalter/.local/bin"
to ~/.profile
in order to call meson builddir without explicitly giving the full path to meson. According to https://mesonbuild.com/Quick-guide.html#compiling-a-meson-project I should
cd
to the root directory of the source code. I did so:
cd /home/verwalter/Downloads/libfprint/libfprint-master
apply meson builddir && cd builddir
from there
do further steps.
Step 2 failed with these messages:
The Meson build system
Version: 0.61.1
Source dir: /home/verwalter/Downloads/libfprint/libfprint-master
Build dir: /home/verwalter/Downloads/libfprint/libfprint-master/builddir
Build type: native build
Project name: libfprint
Project version: 1.94.2
C compiler for the host machine: cc (gcc 9.3.0 "cc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0")
...
meson.build:68: WARNING: Consider using the built-in warning_level option instead of using "-Wall".
meson.build:69: WARNING: Consider using the built-in warning_level option instead of using "-Wall".
Found pkg-config: /usr/bin/pkg-config (0.29.1)
...
Run-time dependency gobject-2.0 found: YES 2.64.6
Did not find CMake 'cmake'
Found CMake: NO
Run-time dependency gusb found: NO (tried pkgconfig)
meson.build:84:0: ERROR: Dependency "gusb" not found, tried pkgconfig
A full log can be found at /home/verwalter/Downloads/libfprint/libfprint-master/builddir/meson-logs/meson-log.txt
What did I miss?
What's the next step to correct this?