evtest and libevdev

[Thomas Weißschuh]

Hi everybody,

while playing with Linux input subsystem I stumbled up the fact that evtest does
not use libevdev.
This became apparent as that evtest was not able to resolve the string name of
a keycode (KEY_MACRO1) which however was known to libevdev.

This was surprising as just before I read the following snippet in libevdev.h:

/*
 * libevdev is essentially a `read(2)` on steroids for `/dev/input/eventX`
 * devices. It sits below the process that handles input events, in between
 * the kernel and that process. In the simplest case, e.g. an evtest-like tool
 * the stack would look like this:
 *
 *      kernel → libevdev → evtest
 */

Are there non-obvious reasons for evtest not using the functionality from libevdev?
(Especially the update-heavy name resolution)

Regards,
Thomas