Files
lcdproc/INSTALL
T

239 lines
8.5 KiB
Plaintext
Raw Normal View History

-- REALLY-QUICK START --------------------------------------------------
1999-12-09 23:15:14 +00:00
If you're in a desperate hurry type:
./configure --enable-drivers=all
make
1999-12-09 23:15:14 +00:00
And if you start wondering why it doesn't work, come back and read the
rest of the file. 8)
-- PREREQUISITES -----------------------------------------------------
1999-12-09 23:15:14 +00:00
First read the README if you haven't already.
2002-05-20 21:57:46 +00:00
Please take a few minutes to read the user guide located at
2002-05-28 11:30:05 +00:00
http://lcdproc.sourceforge.net/docs/
2002-05-20 21:57:46 +00:00
2002-05-28 11:30:05 +00:00
For the details on supported platforms, see the PLAFORM SPECIFIC section
of this file.
1999-12-09 23:15:14 +00:00
2002-05-28 11:30:05 +00:00
In order to compile LCDproc, you'll need the following programs:
an ANSI C compiler, we recommend GCC. Most Linux or BSD systems come
with GCC.
2002-02-21 22:50:12 +00:00
GNU Make. It is available for all major distributions. If you want to
compile it yourself, see http://www.gnu.org/software/make/make.html .
2002-02-21 22:50:12 +00:00
The GNU autotools, that is automake and autoconf. It is available for
all major distributions. If you want to compile it yourself, see
http://sources.redhat.com/automake/ and
http://sources.redhat.com/autoconf/ .
2002-02-21 22:50:12 +00:00
-- DISPLAYS -----------------------------------------------------------
2002-02-21 22:50:12 +00:00
Many different displays (or better said: output devices) are supported.
Some of these devices also support input, for example with a keypad.
2002-05-28 11:30:05 +00:00
There are drivers for input-only devices, too.
2002-02-21 22:50:12 +00:00
For LCDd (the server) to use the device, it needs to load a driver. The
drivers are so called 'shared modules', that usually have an extension
of .so . The drivers to be loaded should be specified in the config file
(by one or more Driver= lines), or on the command line. The command line
should only be used to override things in the config file. The drivers
should be in a directory that is indicated by the DriverPath= line in
the configfile.
Depending on what kind of LCD display that you have, there are several
sources for informations. If your LCD display came with a manual, this
2002-02-21 22:50:12 +00:00
is a great place to start. If you don't have a manual, then you must
find out what kind of display this is, and check the related
informations:
2002-05-28 11:30:05 +00:00
HD44780 and compatible:
read the HD44780 section in the LCDproc User's Guide (docs/lcdproc-user)
2002-02-21 22:50:12 +00:00
or alternatively see http://www.robijn.net/lcdproc/
2002-05-28 11:30:05 +00:00
STV5730: http://www.usblcd.de/lcdproc/
SED1520: http://www.usblcd.de/lcdproc/
2002-05-28 11:30:05 +00:00
If you still have problems you could take a look at the comments in the
driver source code in server/drivers/. You may have some good indications
there.
You may want to take a look at LCDproc's hardware page at
2002-08-11 19:32:57 +00:00
http://lcdproc.org/hardware.php3 for details. Several
different types of displays are now supported.
1999-12-09 23:15:14 +00:00
-- BUILDING LCDPROC -------------------------------------------------
1999-12-09 23:15:14 +00:00
2002-05-28 11:30:05 +00:00
--- Preparing a CVS distro ---
If you retrieved these files from the CVS, you will first need to run:
sh ./autogen.sh
--- Configuration ---
The simplest way of doing it is with:
./configure
But it may not do what you want, so please take a few seconds to type:
./configure --help
And read the available options, especially --enable-drivers
1999-12-09 23:15:14 +00:00
--- Compilation ---
Run make to build the server and all clients
make
1999-12-09 23:15:14 +00:00
2002-05-28 11:30:05 +00:00
If you only want to compile the clients, you can omit to compile the
server:
cd shared
make
cd ../clients
make
1999-12-09 23:15:14 +00:00
2002-05-28 11:30:05 +00:00
Similarly, if you only want to compile the server, you can omit to
compile the clients:
cd shared
make
cd ../server
make
1999-12-09 23:15:14 +00:00
2002-05-28 11:30:05 +00:00
Depending on your system, LCDproc will build in a few seconds to a
few minutes. It's not very big.
If you want, you can install it (if you're root) by typing:
make install
1999-12-09 23:15:14 +00:00
This will install the binaries and the man pages in the directory you
specified in configure.
2002-05-28 11:30:05 +00:00
You may have to copy the configuration file (LCDd.conf) to /etc
(or /usr/local/etc) manually.
1999-12-09 23:15:14 +00:00
-- PLATFORM SPECIFIC ------------------------------------------------
1999-12-09 23:15:14 +00:00
2002-02-21 22:50:12 +00:00
The lcdproc crew has tried to support a number of platforms. Platforms
that are very non-standard are not and will probably never be supported.
Both server & drivers and clients have their own difficulties in
porting. Here's are the prerequistes for both:
--- Client ---
The client should run on any POSIX compliant system.
It has been sucessfully tested on:
Linux 2.2.x, Linux 2.4.x, NetBSD 1.5, OpenBSD 3.0
2002-08-11 19:32:57 +00:00
In the future, we want it to run on Windows, MacOS and others.
2002-02-21 22:50:12 +00:00
--- Server ---
2002-05-28 11:30:05 +00:00
The server needs to talk to the LCD display. At this time, it works
2002-02-21 22:50:12 +00:00
on very little more than on the Intel i386 (PC Compatible)
architecture. It has been sucessfully tested on:
Linux 2.2.x, Linux 2.4.x, NetBSD 1.5, OpenBSD 3.0
Here are some comments specific to each platform that LCDproc has been
tested on.
--- Linux ---
Nothing special to say, everything should go well.
2002-02-21 22:50:12 +00:00
You may not be able to compile all drivers on something else than i386
if your linux installation does not have ioperm, inb and outb commands.
2002-05-28 11:30:05 +00:00
./configure should leave all drivers that need those functions out
(drivers for parallel port displays), so that LCDd should compile anyway.
--- NetBSD ---
2002-05-28 11:30:05 +00:00
You need to use GNU Make instead of NetBSD's make.
Remember to type gmake instead of make to compile LCDproc.
2002-02-21 22:50:12 +00:00
The server will probably only compile on NetBSD/i386.
If you try to run LCDd and you get this error:
Bus error (core dumped)
2002-05-28 11:30:05 +00:00
It is likely that you did not have the right permission to access the ports.
Try starting the program as root.
--- OpenBSD ---
2002-05-28 11:30:05 +00:00
You need to use GNU Make instead of OpenBSD's make.
2002-02-21 22:50:12 +00:00
Remember to type gmake instead of make to compile LCDproc.
2002-05-28 11:30:05 +00:00
The server will probably only compile on OpenBSD/i386.
--- FreeBSD ---
2002-05-28 11:30:05 +00:00
It should compile fine on i386.
2002-02-21 22:50:12 +00:00
--- Other platforms ---
If the build process fails, but you do know how to link a loadable
module by hand, you can add the appropriate flags etcetera into
acinclude.m4. Experience required. Please let us know if you got it
working on a previously unsupported system, so we can include it in a
next release.
-- RUNNING LCDPROC -----------------------------------------------------
--- Configuration file ---
The first thing that you need to do is to modify the configuration file
for your server. A example file (LCDd.conf) is available in the tarball.
The comments present in this file should give you indications on what
to do.
--- Starting the server ---
If you're in the LCDproc source directory, and have just built it, run:
server/LCDd -c path/to/config/file
2002-05-28 11:30:05 +00:00
You can find out what drivers were compiled by running "LCDd -h".
Note that you cannot use more than one display driver at the same time.
2002-05-28 11:30:05 +00:00
For security reasons, LCDd by default only accepts connections from
localhost (127.0.0.1), it will not accept connections from other computers on
your network / the Internet. You can change this behavior in the
configuration file.
--- Starting the client(s) ---
1999-12-09 23:15:14 +00:00
2002-02-21 22:50:12 +00:00
Then, you'll need some clients. LCDproc comes with a few, of which the
'lcdproc' client is the main client:
clients/lcdproc/lcdproc C M T X &
1999-12-09 23:15:14 +00:00
2002-02-21 22:50:12 +00:00
This will run the LCDproc client, with the [C]pu, [M]emory,
[T]ime, and [X]load screens. The ampersand (&) puts it in the
background.
1999-12-09 23:15:14 +00:00
By default, the client tries to connect to a server located on localhost
and listening to port 13666. To change this, use the -s and -p options.
1999-12-09 23:15:14 +00:00
-- PUTTING LCDPROC IN SYSTEM STARTUP -----------------------------------
1999-12-09 23:15:14 +00:00
It's nice to have LCDproc start when the computer boots, so here's how
to do it:
2002-05-28 11:30:05 +00:00
WARNING: Make sure you have modified the configuration file (/etc/LCDd.conf)
so that LCDd enters the background mode.
Otherwise LCDd will lock your system.
Slackware:
1999-12-09 23:15:14 +00:00
Add lines to your /etc/rc.d/rc.local, such as the following:
2002-05-28 11:30:05 +00:00
echo "Starting LCDd..."
/usr/local/sbin/LCDd -c /etc/LCDd.conf
echo "Starting lcdproc..."
1999-12-09 23:15:14 +00:00
/usr/local/bin/lcdproc C M X &
2002-05-28 11:30:05 +00:00
Debian:
- Copy (as root) the debian init script from the scripts/ direcory of the
sources to /etc/init.d
(cp scripts/init-lcdd.debian /etc/init.d/lcdd && \
cp scripts/init-lcdproc.debian /etc/init.d/lcdproc)
- Run (as root): update-rc.d lcdd defaults
2002-02-21 22:50:12 +00:00
This will create symlinks to start and stop the daemon, resp.
from /etc/rc[2-5].d/S50lcd to /etc/init.d/lcd, and from
/etc/rc[016].d/K50lcd to /etc/init.d/lcd.
2002-05-28 11:30:05 +00:00
- Run (as root): update-rc.d lcdproc defaults
This will create symlinks to start and stop the lcdproc client, resp.
from /etc/rc[2-5].d/S50lcdproc to /etc/init.d/lcdproc, and from
/etc/rc[016].d/K50lcdproc to /etc/init.d/lcdproc.
1999-12-09 23:15:14 +00:00
2002-05-28 11:30:05 +00:00
Redhat / Mandrake:
- Copy the scripts:
cp scripts/init-lcdd.rpm /etc/rc.d/init.d/lcdd && \
cp scripts/init-lcdproc.rpm /etc/rc.d/init.d/lcdproc)
- enable the scripts with e.g. linuxconf or create the symlinks manually
1999-12-09 23:15:14 +00:00
2002-05-28 11:30:05 +00:00
That's all the OS`s we've actually done this with so far..