Age | Commit message (Collapse) | Author |
|
This reverts commit 326e15a8ed97a22f2fe52d203896763d75f93c2c.
The issue in:
http://git.kernel.org/?p=linux/hotplug/udev.git;a=commit;h=7fa9bb9dbf538bf3c8a25a6699f65a8ac9cc8bbf
still exists. We need to find a reliable way not to break
"make distcheck" here.
|
|
Now use libudev to clean up hardcoded /sys/ and /device/ paths, and to also
support direct input device arguments. Now both "input4" and "event4" will
work.
|
|
gudevenumtypes.h won't be under $(top_srcdir) when built out-of-tree
from GIT.
Signed-off-by: Scott James Remnant <scott@ubuntu.com>
|
|
input_id probes input/event devices for their class (keyboard, keys, mouse,
touchpad, tablet, joystick). This is based on the corresponding hal code in
hald/linux/device.c, input_test_{abs,rel,...}.
This should provide enough functionality to get hal-less X.org working (which
in particular needs to know exactly which devices are touchpads).
Replace the brittle hacks in 60-persistent-input.rules with checking for the
new ID_INPUT_* flags. This keeps the old ID_CLASS properties for now (but they
are to be removed later on).
Note: The current code has several hacks still, which are to be replaced with
proper libudev calls later on.
|
|
This reverts commit b15b08913800c4a2fad6530becca55b896f66984.
This breaks "make distcheck". The header is distributed in the tarball,
and does not live in builddir.
|
|
|
|
|
|
Actually dev_t is an unsigned quad type (e.g. 64-bit even on 32-bit
x86) so defining it to be an integer is wrong and not future
proof. Thus, redefine it to actually be a dev_t (as originally wanted)
and instead add a work-around for GNOME bug #584517, see
https://bugzilla.gnome.org/show_bug.cgi?id=584517
for details. This way, GObject Introspection will still work.
This change is technically an API/ABI break but
- all released GUdev versions requires the user to understand that
the API/ABI is unstable by requiring the G_UDEV_API_IS_SUBJECT_TO_CHANGE
symbols to be defined
- functions using GUdevDeviceNumber are rarely used
so we don't bump the so number.
Signed-off-by: David Zeuthen <davidz@redhat.com>
|
|
|
|
Don't use the [[:space:]] syntax in awk calls' regex, since that's GNU awk
specific. Thanks to Alan Jenkins for finding this.
|
|
Signed-off-by: David Zeuthen <davidz@redhat.com>
|
|
https://launchpad.net/bugs/215035
|
|
This fixes commit a05cd7ea3e582c9bf9680492e73687ea56cdd864
|
|
This introduces a new rules section for USB keyboards, too.
https://launchpad.net/bugs/215035
|
|
|
|
Workaround for https://bugzilla.gnome.org/show_bug.cgi?id=562885
|
|
It's provided by the kernel since 2.6.23.
|
|
Unfortunately KEY_COFFEE is the canonical name in linux/input.h, and the more
sensible KEY_SCREENLOCK is an alias. Manually override this particular case,
since it's better to have "screenlock" in keymaps.
However, we still keep the automatic filtering for the general case, to avoid
introducing this problem again when input.h changes.
|
|
More than one key name was mapped to the same key, due to linux/input.h
defining some aliases (in particular, KEY_HANGUEL, KEY_SCREENLOCK,
KEY_MIN_INTERESTING). These caused hash table collisions.
Changed the generation of the tables to ignore these aliases, and updated all
keymaps to use the canonical name.
This was detected by llvm-clang-analyzer. Thanks to Lennart Poettering for
doing these checks and pointing this out!
https://launchpad.net/bugs/426647
|
|
Since the recent Makefile.am rework both usb-db and pci-db were built to
read the usb.ids database file. This fix makes sure pci-db properly
reads pci.ids instead.
Originally pointed out by Marco d'Itri.
|
|
https://launchpad.net/bugs/407940
|
|
|
|
|
|
|
|
Pass the path to keys.txt as second parameter of check-keymaps.sh so that
it can be found in the right path.
|
|
Since the check-keymaps.sh script checks for validity the source directory
and the Makefile.am file, instead of running it during user-oriented “make
check”, run it during developed-oriented “make distcheck”.
An invalid keymap will abort the execution which will prevent shipping
an incomplete Makefile.am.
To properly support out-of-source builds, pass as single parameter to the
test the path to the source directory.
|
|
This removes another file from the distribution, since we're not using it
anywhere else but the top-level Makefile.am file.
|
|
This avoids an '80s C prototype which caused a warning during our build.
|
|
|
|
When building in-source, the source and header files are in the same
directory, but they are not in out-of-source.
|
|
Since the library is in a subdirectory, it has to know where to look for
it.
|
|
|
|
|
|
|
|
The Introspection rules are not tested yet; more touch-ups have been made
for them.
|
|
Since gudev conditionally installs further pkg-config data, we have to set
it before the condition might be expanded.
|
|
|
|
Slight adjustment around the tests and the rules for the new working
directory.
|
|
|
|
|
|
A little fix is needed for the udev-test.pl script (to be called with the
proper path), but this allows for the test binaries to be only built when
running the tests themselves.
|
|
Instead of using multiple recursive Makefile.am files, use a single
Makefile.am that sets and builds all the basic suite of libraries and
binaries for udev. This reduces the number of files in the source tree, and
also reduces drastically the build time when using parallel-make.
With this setup, all the compile steps will be executed in parallel, and
just the linking stage will be (partially) serialised on the libraries
creation.
|
|
|
|
|
|
GObject libudev access. Initial version from Bastien Nocera, current
version by David Zeuthen.
|
|
The build of extras with larger external dependencies is wrapped in:
--enable-extras
|
|
|
|
|
|
|
|
[...] running the command
`make maintainer-clean' should not delete `configure' even if
`configure' can be remade using a rule in the Makefile. More
generally, `make maintainer-clean' should not delete anything that
needs to exist in order to run `configure' and then begin to build
the program. This is the only exception; `maintainer-clean' should
delete everything else that can be rebuilt.
|