<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <HEAD> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <TITLE>LIRC - Linux Infrared Remote Control</TITLE> <LINK REL="stylesheet" TYPE="text/css" HREF="lirc.css"> <LINK REL="shortcut icon" HREF="../images/favicon.ico"> <META NAME="description" CONTENT="LIRC - Linux Infrared Remote Control"> <META NAME="keywords" CONTENT="linux remote control, multimedia"> <META charset="UTF-8"> </HEAD> <body> <TABLE CLASS="menu"><TR> <TD CLASS="menu"><IMG class="menuimg" SRC="../images/diode.gif" ALT="LIRC icon" ALIGN="LEFT"></TD> <TD><IMG class="menuimg" SRC="../images/lirc.gif" ALT="LIRC logo" ALIGN="RIGHT"></TD> </TR></TABLE> <a name="api_general"></a><hr> <h1>Lirc API:s</h1> The LIRC lib/ directory is indeed code used in various places. It offers three views: <ul> <li>External applications uses the lirc_client.h header file and links to liblirc.so using -llirc. This is a mature, reasonably stable interface. See the <a href="lirc_client.html">client api</a> </li> <li>User space drivers includes the lirc_driver.h header and links to liblirc_driver.so using -llirc_driver. The other way around lirc accesses the driver as defined in the driver.h file (the driver structure). This interface is new and will probably need some time to stabilize. See the <a href="driver-api.html">driver api</a> </li> <li>Internal lirc applications includes the lirc_private.h header file and links to liblirc_private.so using -llirc_private. This interface is subject to change without notice, and external applications are strongly adviced to not use it.</li> </ul> <p class="footer"> [<A HREF="http://www.lirc.org/">LIRC homepage</A>] </p> </body> </html>