-
Bastien Nocera authored
There are no parts of libfprint that are so resource intensive that we'd want to disable logging. This avoids (hopefully rare) cases where compiled versions of libfprint are distributed with logging completely disabled, and thus can't be debugged.
63e5d564