uinput-mapper

mirror of https://github.com/moparisthebest/uinput-mapper synced 2024-11-10 10:55:01 -05:00

Go to file

Merlijn Wajer 4323e92a13 More networked code; experimental config support. read.py now deprecates test.py I went with optparse rather than argparse to support Python <2.7. Switching to argparse later should not be that hard. Configurations still need to be extended with, among other things: * Name for the device		2013-05-10 11:05:31 +02:00
confs	Small and simple evtest-like program.	2013-04-18 00:50:28 +02:00
py	More networked code; experimental config support.	2013-05-10 11:05:31 +02:00
read-device	Initial input-clone	2013-01-16 02:28:36 +01:00
config_functions.h	Small and simple evtest-like program.	2013-04-18 00:50:28 +02:00
config.h	Small and simple evtest-like program.	2013-04-18 00:50:28 +02:00
Makefile	Small change.	2013-02-13 00:34:09 +01:00
map.c	Fix compilation error.	2013-04-25 20:51:33 +02:00
README.rst	And make it rst syntax.	2013-03-14 13:41:05 +01:00
TODO	Small TODO.	2013-01-27 01:10:57 +01:00

README.rst

uinput-mapper
=============

uinput-mapper maps input devices to new virtual input devices, using (as implied
by the name /dev/uinput[1]).

Configuration is done in the C language (preprocessor mostly) to keep things
simple and clean.

Comments, feedback, success stories, bugs and rants all welcome.


[1] Or /dev/input/uinput depending on the OS.

Building
========

Simply:

    make

to build the program. But you probably want to configure it first.

Configuration
=============

Configuration is done in the C preprocessor (and just C), recompile if you make
changes. Symlink "config.h" to an configuration file in confs/ (or just create
it). The example config confs/techinc-arcade.h is documented and should
(hopefully) be clear enough.

Mind you that invalid configurations can lead to compile-time and run-time
errors.

Bugs
====

None that I am aware of, but if you find some please drop me a mail at
http://wizzup.org.