63e5d56441
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.
25 lines
718 B
Meson
25 lines
718 B
Meson
option('drivers',
|
|
description: 'Drivers to integrate',
|
|
type: 'string',
|
|
value: 'all')
|
|
option('udev_rules',
|
|
description: 'Whether to create a udev rules file',
|
|
type: 'boolean',
|
|
value: true)
|
|
option('udev_rules_dir',
|
|
description: 'Installation path for udev rules',
|
|
type: 'string',
|
|
value: 'auto')
|
|
option('x11-examples',
|
|
description: 'Whether to build X11 example applications',
|
|
type: 'boolean',
|
|
value: true)
|
|
option('debug_log',
|
|
description: 'Debug message logging',
|
|
type: 'boolean',
|
|
value: false)
|
|
option('doc',
|
|
description: 'Whether to build the API documentation',
|
|
type: 'boolean',
|
|
value: true)
|