|Name||Modified||Size||Downloads / Week||Status|
|Totals: 7 Items||5.8 kB||18|
maintenance release: Refreshing automake files and installation. Alec Leamas
maintenance release: now using automake Christopher Bartelmus
fixed gcc 4.0 compile error better IRA-3 support
v0.1 1998/11/05 Initial release.
by Tom Wheeley firstname.lastname@example.org
Copyright and Licensing
libirman v0.4.5, Copyright (C) 1998,1999 Tom Wheeley email@example.com
The files which make up the library are covered under the GNU Library General Public License, which is in the file COPYING.lib.
The files which make up the test programs and the documentation are covered under the GNU General Public License, which is in the file COPYING.
libirman is a library for accessing the IRMAN hardware from Linux and other Unix systems.
Currently the package is mainly for advanced users and developers; this does not mean that less experienced users will not be able to use it, but that there are not a lot of applications for libirman at the moment, and that if you run into problems you may have difficulty fixing things.
Read the file TECHNICAL to see how libirman works, and how to use it in your applications.
Use with LIRC
For general applications programming, the preferred interface for infra-red control is `lirc', as lirc supports multiple programs sharing the same infra-red receiver. It does this by providing a socket based interface to which several programs can connect.
lirc uses libirman to interface with the Irman hardware, so in single use applications directly using libirman is simpler and uses less system resources. Currently, lirc only works on Linux systems, so programs written using libirman directly are more portable.
To use libirman v0.4.2 with lirc you will need v0.5.5 of lirc or greater. Versions 0.4.1, 0.4.1a and 0.4.1b can be used with earlier versions of lirc. The reason for this is that the Irman lirc driver daemon, lirmand, has been moved from the libirman package to the lirc package, and the version distributed with libirman 0.4.1 is not compatible with libirman v0.4.3.
my homepage http://www.tsys.demon.co.uk (defunct)
libirman homepage http://www.evation.com/libirman/ (defunct)
Irman hompage http://www.evation.com/irman/ (defunct, see LIRC homepage)
LIRC homepage http://www.lirc.org/
To build libirman, run
autoreconf -fi ./configure make make install
The autoreconf step is optional, but recommended. You can also build without cluttering the sources:
autoreconf -fi mkdir _build; cd _build ../configure make make install
You may well like to check the available options to configure by typing
the most important are: --prefix and --enable-swtest
This will create the following important files:
By default they are installed in /usr/local. If you do not use the --prefix
configure' then you will need to be root to runmake install'.
Firstly, you should test that the system works. Run `test_io' with the hardware plugged in and see if code numbers appear on the screen when you press buttons on your remote control.
Once the basic hardware works, you should run
test_func' to help you set up
libirman for your remote control. Make sure you have available virtual
consoles, or are running eitherscreen' or `X' or some other similar
irman.conf' should be copied to /usr/local/etc/irman.conf. You may
want to copy this to~/.irmanrc'. libirman searches first for ~/.irmanrc,
and if that is not found reads /usr/local/etc/irman.conf.
Press each button on your remote control, and note down the number printed - you need to add a `bind' line to your irmanrc file, noting the naming convention used:
bind manufacturer-device-button code
once you have entered in the data for your remote control, you should change the workman-* alias lines to point to your remote control's entries.
You may also like to specify the default port in the config file.
Once you have entered in names into your irman config file, try running
test_name' to see if the bindings have worked. (You should see the names
you gave on thebind' lines appear as you press the buttons).
To see if
workmanir' works, make sure you are already runningworkman', then
workmanir' and try pressing buttons. Make sure you have changed thealias' lines in your irman.conf.
If you want to test libirman without using the irman hardware, you can run:
`./configure --enable-swtest; make'
which will create libirman_sw.a and programs *_sw (except test_io). These will ask you to enter a twelve digit hex code to represent a code instead of querying the hardware.
If you compile libirman with the define -DDEBUG_COMM then every byte read/written from the serial port is printed to stdout. (to do this run: CPPFLAGS=-DDEBUG_COMM ./configure; make clean; make) First technology demonstrator, `IRIO.C' essentially consisted of (what is now) irio.c and test_lo.c
Thankyou to the following:
Christoph Bartelmus firstname.lastname@example.org maintainer of LIRC project.
Bill Ryder email@example.com fix to make it work on SGI Indy's (and other Unix boxes)
MiniDisc, http://www.minidisc.org for being just so damn cool.