Requires some .gitignore pattern removal too and an autotools fix to actually
dist the man pages.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Remove the includsion of sys/signalfd.h again, it hasn't been needed
since cca90938 and was accidentally re-added, probably as a mismerge,
in a40e014e.
Signed-off-by: Niclas Zeising <zeising@daemonic.se>
And fix the script to sync the headers up so it syncs event codes for both bsd
and linux, but only syncs input.h for linux.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Add two FreeBSD specific tests:
test_uinput_check_devnode_bsd checks that libevdev_uinput_get_devnode()
returns something sensible. This is modelled on the Linux test
test_uinput_check_syspath_name, but uses devnode instead of syspath, since
reeBSD doesn't have sysfs.
test_uinput_check_syspath_bsd checks that libevdev_uinput_get_syspath()
always returns NULL.
Signed-off-by: Niclas Zeising <zeising@daemonic.se>
FreeBSD does not support force feedack events. Disable the test for
this event when running on FreeBSD.
Signed-off-by: Niclas Zeising <zeising@daemonic.se>
FreeBSD does not have CLOCK_MONOTONIC_RAW, instead use
CLOCK_MONOTONIC_FAST. This test checks that libevdev_set_clock_id()
fails when called with CLOCK_MONOTONIC_[RAW,FAST].
Signed-off-by: Niclas Zeising <zeising@daemonic.se>
Implement a FreeBSD version of fetch_syspath_and_devnode().
FreeBSD does not have sysfs, so instead fetch the device node directly
as as this matches with what is returned by the UI_GET_SYSNAME ioctl().
Since there is no sysfs, libevdev_uinput.syspath will always be set to NULL.
If the ioctl fail, return -1 from fetch_syspath_and_devnode(), since
there is no other way to figure out the device node path.
Signed-off-by: Niclas Zeising <zeising@daemonic.se>
Move the definition of SYS_INPUT_DIR to where it is used, instead of at
the top of the file, to make it easier to find.
Undefine it at the end of usage to avoid accidental uses.
Signed-off-by: Niclas Zeising <zeising@daemonic.se>
Use baename(argv[0]) to get the program name (for usage), instead of
using program_invocation_short_name, which only exists on Linux, not
FreeBSD.
Signed-off-by: Niclas Zeising <zeising@daemonic.se>
Remove signalfd() use from the mouse-dpi-tool and touchpad-edge-detector
tools, in favor of using plain old signals.
FreeBSD does not have signalfd() without pulling in external libraries,
and with this change these tools can be compiled on FreeBSD.
Instead of providing two implementations, one using signalfd() and one
using signal(), just use the signal() implementation everywhere as it is
more portable.
Signed-off-by: Niclas Zeising <zeising@daemonic.se>
Add FreeBSD compatible input.h and uinput.h files.
This is done by moving the linux files to include/linux/linux, adding
the freebsd versions in include/linux/freebsd, and then changing
include/linux/[u]input.h to pull in the right one depending on which OS
we are compiling on.
Make sure that the build infrastructure in meson.build and
autoconf.ac/Makefile.am uses the correct files when building and as
dependency for targets, and ensure that make-event-names.py get the
correct files as arguments.
A similar change has been done in libinput in
61f3e3854458c556a01fb05d7abb22733fd2b7c1
Signed-off-by: Niclas Zeising <zeising@daemonic.se>
Don't hardcode /bin/bash, use /usr/bin/env bash instead, since not all
platforms install bash as /bin/bash.
FreeBSD, as an example, installs bash in /usr/local/bin/bash by default.
Signed-off-by: Niclas Zeising <zeising@daemonic.se>
This gives the developer enough time to file an MR after pushing a branch.
Having this run in the first stage means we get false positives because no MR
has been filed yet when the job is run.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
ci-templates now has a new tool ci-fairy that replaces our jinja generation
script with something (eventually) unified across project repositories. Let's
move the files to the expected locations .gitlab-ci/config.yml and
.gitlab-ci/ci.template.
ci-fairy also has a wrapper to delete images, let's start using that.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
On a device with more than 256 slots we would read (and copy) past our changes
stack-allocated changes array. Fix this by capping to MAX_SLOTS though this
also requires us to memset the target where it is larger than MAX_SLOTS.
There are no real devices with 256+ slots, so this is a theoretical issue
only.
Fixes#11
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Fixes:
../test/test-common.h: In function ‘print_event’:
../test/test-common.h:97:6: error: ‘const struct input_event’ has no member named ‘input_event_sec’
ev->input_event_sec,
^
../test/test-common.h:98:6: error: ‘const struct input_event’ has no member named ‘input_event_usec’
ev->input_event_usec,
^
../test/test-common.h:102:6: error: ‘const struct input_event’ has no member named ‘input_event_sec’
ev->input_event_sec,
^
../test/test-common.h:103:6: error: ‘const struct input_event’ has no member named ‘input_event_usec’
ev->input_event_usec,
^
Signed-off-by: Peter Seiderer <ps.report@gmx.net>
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Fixes the following compile failure with old toolchains and meson
build (autotools build not affected):
../tools/mouse-dpi-tool.c: In function ‘handle_event’:
../tools/mouse-dpi-tool.c:115:13: error: ‘const struct input_event’ has no member named ‘input_event_sec’
m->us = ev->input_event_sec * 1000000 + ev->input_event_usec;
^
../tools/mouse-dpi-tool.c:115:45: error: ‘const struct input_event’ has no member named ‘input_event_usec’
m->us = ev->input_event_sec * 1000000 + ev->input_event_usec;
^
Signed-off-by: Peter Seiderer <ps.report@gmx.net>
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Let's not duplicate the functionality, use the upstream templates because
they'll actually see improvements over time.
Define two jobs, one that is the ifnot-exists job and one that is the normal
container-build job. The second one only runs on schedules.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
gitlab doesn't support double-nested variables so we can assume that these
variables don't need further expansion
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
This is a test commit only to speed things up when testing the container-clean
phase. In the real instance, we don't want to remove our containers until the
test suite successfully completes on the new container.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
