DevSlashLirc — Object oriented access to
This library makes objects from
/dev/lirc-hardware. These objects have properties like
indicating the capabilities of the currently connected hardwarec, and methods like
for sending and receiving. See the examples in
As opposed to standard C/Lirc, where a device is opened, and it "turns out" that it is "mode2" or "lirccode",
here the user has to decide if he wants a mode2 or lirccode device, and open it with the appropriate class.
This will fail if the connected hardware does not have the expected properties. For this,
there are the concrete classes
Mode2LircDevice (modeling a "mode2" device, i.e. with the possibility of
handling IR signals with "arbitrary" timings), and
LircCodeLircDevice (modeling a "LircCode" device, i.e.
one that can only use IR signals from its own set, and codes them on an integer, representing the IR
signal.) The latter class is presently not completely implemented.
The classes may be instantiated multiple times, but of course only one can open a particular device file at a particular time.
The core library is written in C++, using classes and the stdc++ library.
There are no other dependencies. In particular, there is no dependency of the
Lirc sources, includes, or libraries. Only
man 4 lirc, which is considered
belonging to the kernel, is included. The C++ code is documented using doxygen.
The C++-code uses the ("non-portable")
#pragma once instead of the traditional
The C++ code is compiled into a shared library. This can be linked into application programs (see the test
src/test/c++) or used as a JNI library for accessing it from Java.
Also a static library is built.
man 4 lirc shows, there is a large number of hardly ever implemented properties supported. I have followed
the "agile" commandment maximize the amount of work not done, and simply ignored the ones not useful or not
The code should compile on any platform supporting
/dev/lirc, possibly after adapting the Makefile
(see issue #2).
A natural extension would be to extend the library to support Lirc plugin drivers. This is discussed in issue #3).
There is also a branch containing some work in this directon,
Maven is used to compile the Java parts. A Makefile compiles the C++ code, and also invokes the Maven process. Redundantly, to build, just issue the command
On an x86_64, this will build the libraries for x86_32 and x86_64.
To build for another architecture without using a cross compiler,
log in to an appropriate host, cd to
src/main/c++, and issue the command
make clean all
on that host.
Then copy the thus created
libdevslashlirc.so to a desired location.
creates the Doxygen and Javadoc documentation.
The code is entirely written from scratch (not counting the branch
There is no "install". Just copy the
so file, the
jar file, and possibly the
*.h files to anywhere you like.
(Or use maven instead for the
For C++ (or a similar language), just link with the shared library
(alternatively the static library
libdevslashlirc.a) in the usual manner.
For Java, copy
libdevslashlirc.so to an "arbitrary" location. In the Java code,
that library must be loaded with
There are two possibilites:
loadLibrary()without arguments, (see
src/test/java/org/harctoolbox/devslashlirc/Mode2LircDeviceNGTest.javafor an example), in which case the actual directory has to be given to the JVM using the
java -Djava.library.path=/usr/local/lib...), or,
loadLibrary(File)with argument, either the path name of the library, or the path name of the containing directory. For example