- 09 Aug, 2018 2 commits
-
-
Peter Hutterer authored
Yes, we should use 'copy'. But that requires 0.47 and that's not an option right now. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Introduced in e428e5e8 Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- 07 Aug, 2018 1 commit
-
-
Peter Hutterer authored
Having this as the generic "synaptics" touchpad in the tests is not helpful, this touchpad is tiny and quite special these days. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- 03 Aug, 2018 1 commit
-
-
Peter Hutterer authored
Cancel any touches that trigger MT_TOOL_PALM. Fixes libinput/libinput#25 Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- 31 Jul, 2018 1 commit
-
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- 30 Jul, 2018 2 commits
-
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
This is a large commit because it's difficult to split this up and we don't care about bisecting here anyway. doxygen is going to produce the API documentation only sphinx is going to produce the prose user (and a bit of developer) documentation. The source split is doc/api and doc/user. Steps performed: - run the doxygen-to-sphinx.sh script to convert all .dox sources to .rst - manually fixed the .rst to render correctly - add a few extra .rst documents to generate the right hierarchy - hook up sphinx-build in meson - add a new @mainpage for doxygen more aimed at developers For the build directory: - sphinx produces /Documentation - doxygen now produces /api/ These need to be manually combined in the wayland-web repo, meson doesn't support subdirectories as output paths within the build dir and the documentation doesn't need to be installed anywhere. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- 23 Jul, 2018 1 commit
-
-
Peter Hutterer authored
Because if we have a heisenbug that can't be reproduced on other machines, having the suppression output in the log can save a lot of time. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- 18 Jul, 2018 1 commit
-
-
unrelentingtech authored
-
- 16 Jul, 2018 4 commits
-
-
unrelentingtech authored
-
unrelentingtech authored
-
unrelentingtech authored
-
unrelentingtech authored
versionsort is a GNU extension, not available on *BSD systems.
-
- 13 Jul, 2018 1 commit
-
-
Peter Hutterer authored
A better, less ambiguous name than just "datadir" Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- 12 Jul, 2018 3 commits
-
-
Peter Hutterer authored
Doing so means we can ditch the specific input list for doxygen and just copy all files over into our builddir/doc/ subdir, then use that subdirectory as input data. This relies on meson putting a subdir() into a subdirectory in the build directory. This isn't technically guaranteed but I also suspect that if meson ever changes that, lots of other projects will break. Even in that case we should build just fine since we now filter for *.h and *.dox and don't copy any other doxygen-commented files into the builddir anyway. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
This hasn't been a real .in file since the autotools removal, so rename it to reflect that. And since we can call it with arguments from meson, let's do so in the most sensible manner - passing the full paths in as required rather than relying on a directory layout within the script. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- 11 Jul, 2018 1 commit
-
-
Peter Hutterer authored
Measuring the trackpoint range has not shown to be sufficient or precise enough to be used as an ingredient for trackpoint acceleration. So let's just switch back to a generic multiplier that we can apply to the input deltas do undo any device-specific lack of scaling. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- 09 Jul, 2018 4 commits
-
-
Peter Hutterer authored
When the meson build type is something other than the debug types, we don't need the special behavior where we adjust executable paths and data dir lookup for tools run directly from the builddir. This avoids leaking the build dir into the final executables. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Doesn't actually do anything but this way they end up in the builddir and can be picked up by ./builddir/libinput measure fuzz, etc. And rename the source files to .py to signal that they are not supposed to be directly executed. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Don't use a custom hack here, just make sure the tool ends up in the builddir so it's picked up by the libinput main tool. This means the PATH isn't set up correctly when called directly (./builddir/libinput-measure-touchpad-pressure) but the workaround is to always use the libinput tool - just as we expect from users. To make it more obvious that we're not supposed to run this directly, rename the source file to .py Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
When running libinput tools from the builddir, look up the subtools in the builddir as well. Otherwise, add the install prefix to the list of lookup locations. This ensures that a) we're running builddir stuff against builddir stuff, but also b) that we're not running builddir stuff against installed stuff because that may give us false positives. The test was squashed in from a separate patch and was Reviewed-by:
Pekka Paalanen <pekka.paalanen@collabora.co.uk> Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- 06 Jul, 2018 2 commits
-
-
Peter Hutterer authored
The libinput/doc/latest is now built automatically from git, so it's good to have a reference to show which commit it was being built from. Add a section to the readme with git commit information that is replaced by meson. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Using files() over a list of hand-constructed paths is the recommended way. But unfortunately doxygen needs its input files as a string list, so we still have to build that list anyway. Still, this way we don't need to hardcode every file with the source root, we just assemble it as we go. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- 05 Jul, 2018 1 commit
-
-
Peter Hutterer authored
Slightly more obvious than just "html". Main motivation here is that we want to provide the documentation as artifact from GitLab's CI, so having it unzip to something slightly more meaningful makes sense. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- 03 Jul, 2018 1 commit
-
-
Peter Hutterer authored
Enables us to easily add more tools where needed and it is more consistent with the existing tools. The commands are now: libinput quirks list libinput quirks validate Fixes #66 Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- 26 Jun, 2018 3 commits
-
-
Peter Hutterer authored
This way we can re-use this from libinput-record instead of having to duplicate all this. Since the two tools use different printfs, just make the actual printing a simple callback. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
This way we can make them execute the list-quirks from the builddir. And it makes it easier to run these tools from the git directory on machines where we have libinput without the quirks. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
These are tests that don't need *any* uinput devices at all. Mark them accordingly and create a new binary that only runs those tests. This way we can run some of the test suite even in containers where we're restricted. Better have 10% tested than none, I guess. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- 20 Jun, 2018 2 commits
-
-
Peter Hutterer authored
"/usr/include/math.h", line 381: error #20 : identifier "_Float32" is undefined # define _Mdouble_ _Float32 Same for a few others. Since we don't actually need those anyway, we can just cast those to the some close-enough sizes. We don't have stdint.h in config.h and meson cannot have a custom #include line in the config object. So let's go with what does the job for now. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Matheus Santana <embs@cin.ufpe.br>
-
Peter Hutterer authored
This will only catch a segfault or some other bug since we don't actually look at the output. But that's still better than not running it at all. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- 18 Jun, 2018 1 commit
-
-
Peter Hutterer authored
Replaced with the quirks files in merge commit 000ac14c Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- 14 Jun, 2018 1 commit
-
-
Peter Hutterer authored
Make the meson -Dtests=false option only apply to the libinput test suite itself which has extra dependencies, etc. The build tests and symbol leak tests should always run. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- 13 Jun, 2018 1 commit
-
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- 08 Jun, 2018 3 commits
-
-
Peter Hutterer authored
All the tests fill fail anyway if the validation fails but this is a quick way to fail everything early. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
These will replace the custom udev rules we currently have in place. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Previously, we had all extra device information ("This is an Apple Touchpad", "This touchpad causes pointer jumps", etc.) in the udev hwdb. The problem with the hwdb is that updating it is nontrivial for the average user and debugging when things go wrong is even harder. Plus, the hwdb has a matching scheme that is unpredictable unless one is familiar with the implementation. This patch set moves the hwdb entries into .ini style text files, with a simple line-based parser. A new libinput list-quirks tool can list the quirks applied to any given device, in --verbose mode it prints all matches as they apply or not apply. The data files are currently unused by libinput, that comes in a later patch. They're installed though, the defaults point to the /usr/share/libinput directory and for *temporary* local overrides the single file /etc/libinput/local-overrides.quirks. Failure to parse any file is a hard failure for the quirks system, but if the local override file doesn't exist that's fine. THIS IS NOT A CONFIGURATION INTERFACE! None of these settings are exposed via the libinput_device_config_* calls. There is no API guarantee for these files, think of them as source code. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- 04 Jun, 2018 1 commit
-
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- 29 May, 2018 1 commit
-
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- 22 May, 2018 1 commit
-
-
Peter Hutterer authored
-