Find a file
Peter Hutterer 7147d5a211 test: don't treat a signal exit as success
WEXITSTATUS() "should be employed only if WIFEXITED returned true", see
wait(2). If a test failed with an abort, WIFEXITED is false and WEXITSTATUS
is... undefined? and apparently zero, so test case failures would cause a
false postive test result.

This doesn't affect a normal test run because check handles the aborts
correctly, but the valgrind invocation with CK_FORK ended up being handle by
litest. So with the result that any abort during valgrind was a silent success
and if there was a memleak in the same process that exited with a signal, the
memleak would be ignored too.

Fixes #267

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2019-05-28 10:32:08 +10:00
.gitlab/issue_templates Update gitlab templates for label renames 2019-01-16 09:34:29 +10:00
.gitlab-ci CI: use templates for Ubuntu 2019-04-01 04:11:20 +00:00
doc meson: group all tests under suite names 2019-05-07 04:48:00 +00:00
include test: replace the USING_VALGRIND env with the valgrind.h header 2019-05-07 04:48:00 +00:00
quirks quirks: add a new Apple vendor ID for Bluetooth devices 2019-04-14 05:51:46 +00:00
src Abstract libwacom database initialization into a single place 2019-05-28 10:32:08 +10:00
test test: don't treat a signal exit as success 2019-05-28 10:32:08 +10:00
tools tools: add --apply-to to debug-events and debug-gui 2019-05-27 11:13:48 +10:00
udev test: install the test device udev rule from a string 2019-03-14 11:28:05 +10:00
.dir-locals.el indentation: add .dir-locals.el for emacs 2018-02-26 18:44:00 +10:00
.gitignore gitignore: ignore gnuplot files 2018-05-10 16:25:40 +10:00
.gitlab-ci.yml test: drop the SKIP_LIBINPUT_TEST_RUNNER environment variable 2019-05-07 04:48:00 +00:00
.vimdir Add .vimdir for libinput-specific settings 2015-05-25 09:17:29 +10:00
CODING_STYLE.md Move CODING_STYLE to markdown 2018-06-14 08:45:56 +10:00
COPYING COPYING: change a cgit to a gitlab URL 2018-06-06 11:17:54 +10:00
meson.build Abstract libwacom database initialization into a single place 2019-05-28 10:32:08 +10:00
meson_options.txt test: make the test suite runner available as installed binary 2019-03-14 12:04:22 +10:00
README.md README: update documentation links 2018-12-22 19:56:21 +02:00

libinput

libinput is a library that provides a full input stack for display servers and other applications that need to handle input devices provided by the kernel.

libinput provides device detection, event handling and abstraction to minimize the amount of custom input code the user of libinput needs to provide the common set of functionality that users expect. Input event processing includes scaling touch coordinates, generating relative pointer events from touchpads, pointer acceleration, etc.

User documentation

Documentation explaining features available in libinput is available here.

This includes the FAQ and the instructions on reporting bugs.

Source code

The source code of libinput can be found at: https://gitlab.freedesktop.org/libinput/libinput

For a list of current and past releases visit: https://www.freedesktop.org/wiki/Software/libinput/

Build instructions: https://wayland.freedesktop.org/libinput/doc/latest/building.html

Reporting Bugs

Bugs can be filed on freedesktop.org GitLab: https://gitlab.freedesktop.org/libinput/libinput/issues/

Where possible, please provide the libinput record output of the input device and/or the event sequence in question.

See https://wayland.freedesktop.org/libinput/doc/latest/reporting-bugs.html for more info.

Documentation

Examples of how to use libinput are the debugging tools in the libinput repository. Developers are encouraged to look at those tools for a real-world (yet simple) example on how to use libinput.

License

libinput is licensed under the MIT license.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: [...]

See the COPYING file for the full license information.

About

Documentation generated by from git commit GIT_VERSION