Basic Installation ================== These are generic installation instructions. The `configure' shell script attempts to guess correct values for various system-dependent variables used during compilation. It uses those values to create a `Makefile' in each directory of the package. It may also create one or more `.h' files containing system-dependent definitions. Finally, it creates a shell script `config.status' that you can run in the future to recreate the current configuration, a file `config.cache' that saves the results of its tests to speed up reconfiguring, and a file `config.log' containing compiler output (useful mainly for debugging `configure'). If you need to do unusual things to compile the package, please try to figure out how `configure' could check whether to do them, and mail diffs or instructions to the address given in the `README' so they can be considered for the next release. If at some point `config.cache' contains results you don't want to keep, you may remove or edit it. The file `configure.in' is used to create `configure' by a program called `autoconf'. You only need `configure.in' if you want to change it or regenerate `configure' using a newer version of `autoconf'. The simplest way to compile this package is: 1. `cd' to the directory containing the package's source code and type `./configure' to configure the package for your system. If you're using `csh' on an old version of System V, you might need to type `sh ./configure' instead to prevent `csh' from trying to execute `configure' itself. Running `configure' takes awhile. While running, it prints some messages telling which features it is checking for. 2. Type `make' to compile the package. 3. Optionally, type `make check' to run any self-tests that come with the package. 4. Type `make install' to install the programs and any data files and documentation. 5. You can remove the program binaries and object files from the source code directory by typing `make clean'. To also remove the files that `configure' created (so you can compile the package for a different kind of computer), type `make distclean'. There is also a `make maintainer-clean' target, but that is intended mainly for the package's developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution. Compilers and Options ===================== Some systems require unusual options for compilation or linking that the `configure' script does not know about. You can give `configure' initial values for variables by setting them in the environment. Using a Bourne-compatible shell, you can do that on the command line like this: CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure Or on systems that have the `env' program, you can do it like this: env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure Compiling For Multiple Architectures ==================================== You can compile the package for more than one kind of computer at the same time, by placing the object files for each architecture in their own directory. To do this, you must use a version of `make' that supports the `VPATH' variable, such as GNU `make'. `cd' to the directory where you want the object files and executables to go and run the `configure' script. `configure' automatically checks for the source code in the directory that `configure' is in and in `..'. If you have to use a `make' that does not supports the `VPATH' variable, you have to compile the package for one architecture at a time in the source code directory. After you have installed the package for one architecture, use `make distclean' before reconfiguring for another architecture. Installation Names ================== By default, `make install' will install the package's files in `/usr/local/bin', `/usr/local/man', etc. You can specify an installation prefix other than `/usr/local' by giving `configure' the option `--prefix=PATH'. You can specify separate installation prefixes for architecture-specific files and architecture-independent files. If you give `configure' the option `--exec-prefix=PATH', the package will use PATH as the prefix for installing programs and libraries. Documentation and other data files will still use the regular prefix. In addition, if you use an unusual directory layout you can give options like `--bindir=PATH' to specify different values for particular kinds of files. Run `configure --help' for a list of the directories you can set and what kinds of files go in them. If the package supports it, you can cause programs to be installed with an extra prefix or suffix on their names by giving `configure' the option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. Optional Features ================= Some packages pay attention to `--enable-FEATURE' options to `configure', where FEATURE indicates an optional part of the package. They may also pay attention to `--with-PACKAGE' options, where PACKAGE is something like `gnu-as' or `x' (for the X Window System). The `README' should mention any `--enable-' and `--with-' options that the package recognizes. For packages that use the X Window System, `configure' can usually find the X include and library files automatically, but if it doesn't, you can use the `configure' options `--x-includes=DIR' and `--x-libraries=DIR' to specify their locations. Specifying the System Type ========================== There may be some features `configure' can not figure out automatically, but needs to determine by the type of host the package will run on. Usually `configure' can figure that out, but if it prints a message saying it can not guess the host type, give it the `--host=TYPE' option. TYPE can either be a short name for the system type, such as `sun4', or a canonical name with three fields: CPU-COMPANY-SYSTEM See the file `config.sub' for the possible values of each field. If `config.sub' isn't included in this package, then this package doesn't need to know the host type. If you are building compiler tools for cross-compiling, you can also use the `--target=TYPE' option to select the type of system they will produce code for and the `--build=TYPE' option to select the type of system on which you are compiling the package. Sharing Defaults ================ If you want to set default values for `configure' scripts to share, you can create a site shell script called `config.site' that gives default values for variables like `CC', `cache_file', and `prefix'. `configure' looks for `PREFIX/share/config.site' if it exists, then `PREFIX/etc/config.site' if it exists. Or, you can set the `CONFIG_SITE' environment variable to the location of the site script. A warning: not all `configure' scripts look for a site script. Operation Controls ================== `configure' recognizes the following options to control how it operates. `--cache-file=FILE' Use and save the results of the tests in FILE instead of `./config.cache'. Set FILE to `/dev/null' to disable caching, for debugging `configure'. `--help' Print a summary of the options to `configure', and exit. `--quiet' `--silent' `-q' Do not print messages saying which checks are being made. To suppress all normal output, redirect it to `/dev/null' (any error messages will still be shown). `--srcdir=DIR' Look for the package's source code in directory DIR. Usually `configure' can determine that directory automatically. `--version' Print the version of Autoconf used to generate the `configure' script, and exit. `configure' also accepts some other, not widely useful, options. 5' href='#n165'>165 166 167 168 169 170 171 172 173 174 175 176 177 
ToDo-List / Wishlist for lcd4linux

// 2000-04-04 Michael Reinelt <reinelt@eunet.at>
// implement some sort of 'graphs', similar to bars, but with a time axis
// can be filled (made up of bars) or not (needs raster graphics)
// done 2001-03-16 -lt.

// 2000-04-04 Michael Reinelt <reinelt@eunet.at>
// write a driver for PNG. This should be the first step towards a WWW-driver.
// Done 2001-03-01 -lt.

2000-04-15 Thomas Skyt Jessen <thskyt@foni.net>
show partition information (used, free, ...)

2000-04-25 Michael Mueller <m.mueller@netsystec.de>
show process information            

// 2000-12-03 Ghassan Matar <gmatar@hexapods.com>
// show other sensors than temperature
// we have to use libsensors instead of parsing the proc files directly
// Refused 2003-08-01 -mr

// 2000-12-03 Ghassan Matar <gmatar@hexapods.com>
// show contents of any text file
// the file should only contain one line, with a fixed format
// there are two possibilities: text and numbers
// numbers can be used for bars, too
// Done 2000-03-08, look at %x -lt

// 2000-12-03 Ghassan Matar <gmatar@hexapods.com>
// accept data from external sources (fifo?)
// Done 2000-03-08, look at %x -lt

// 2001-02-11 Carsten Nau <info@cnau.de>
// connect a LED to a spare pin of the parallel port and show if ISDN
// is online
// Done with GPO's -mr

// 2001-01-27 Axel Ehnert <axel@ehnert.net>
// - display numer of emails in a mailbox
// - display seti@home values
// done.

// 2001-03-05 Leo T�tsch <lt@toetsch.at>
// rename some tokens: %o->%os, %v->%ov, %r->%or, %p->%op,
// will be done with the big config-rework
// done with the "Next Generation Layout"

// 2001-03-05 Leo T�tsch <lt@toetsch.at>
// replace T_EXTENDED with a Flag similar to 'bar'
// rejected, T_EXTENDED does a good job  -mr

// 2001-03-07 Michael Reinelt <reinelt@eunet.at>
// use ppdev instead of ugly outb()
// done 2001-03-14 -mr

// 2001-03-09 Michael Reinelt <reinelt@eunet.at>
// replace udelay() assembly loop with rdtsc (read time stamp counter)
// at least try to....
// done 2001-03-14 -mr

// 2001-03-09 Leo T�tsch <lt@toetsch.at>
// read configuration file earlier (before forking) so that specific drivers
// (especially 'Text') would not fork.
// There's a reason for forking that early, but I forgot...
// done somewhere in mid 2003 MR

// 2001-03-12 Michael Reinelt <reinelt@eunet.at>
// remove USE_OLD_UDELAY after wide testing of new udelay code
// done with the "Next Generation Layout"

// 2001-03-12 Michael Reinelt <reinelt@eunet.at>
// create a NEWS file with changes/enhancements of every release
// done 2001-03-13 -mr

2001-03-14 Leopold Toetsch <lt@toetsch.at>
improve unseen for mbox (check Status:)

// 2001-03-14 Michael Reinelt <reinelt@eunet.at>
// add a new Token 'nc' for 'network collisions'
// done with the "Next Generation Layout"

2001-03-14 Michael Reinelt <reinelt@eunet.at>
add translation tables ('german umlauts' don't 
follow any scheme on most displays)

// 2001-03-15 Leopold Toetsch <lt@toetsch.at>
// Text display has troubles with '\r'
// done 2001-03-16, replace \r,\n with '_'  -lt

// 2001-03-24 Carsten Nau <info@cnau.de>
// change network clients to support different devices
// at the moment the sum of all eth* devices is calculated
// %n* should be extended tokens
// done with the "Next Generation Layout"

// 2001-03-24 Brian Cleven <lcleven@home.com>
// support 40x4 displays with two HD44780 chips on it
// we need another 'Enable' line for this
// this way one could connect two displays to one parallel port, too
// done with 0.9.11 MR

// 2001-05-25 Jens Garthe <outline@xslan.de>
// detect wether curses.h and libncurses is installed, and
// don't include the 'Text'-driver if not.
// _should_ work now 2001-05-31 -lt

// 2001-09-11 Michael Reinelt <reinelt@eunet.at>
// use new extended tokens to split up several data sources
// (CPU, Net, Disk, ISDN, ...)
// e.g. '%nw'  is 'network transmit' for _all_ devices
//     '%n0w' is 'network transmit' for eth0
//     '%n1w' for eth1
// done with the "Next Generation Layout"

// 2001-09-11 Michael Reinelt <reinelt@eunet.at>
// remove bar code from drivers and create a common bar library
// done somewhere in 2003 -mr

// 2001-09-12 Carsten Nau <info@cnau.de>
// make the output for emails shorter (at the moment up to 9999 emails)
// done with the "Next Generation Layout" 

2001-09-13 Michael Reinelt <reinelt@eunet.at>
combine mail.c and mail2.c
if there's an error getting mail info, display "?" instead of "0"

2001-09-14 Michael Reinelt <reinelt@eunet.at>
do not disable mail check in first error
instead use a number of retries
errors can occur in case of short disconnects, but normal operation 
should resume 

2002-02-15 Udo Altmann (udo.altmann@web.de)
support for inversed/blinking text
don't know if displays support this feature...

// 2003-09-08 Michael Reinelt (reinelt@eunet.at>
// at least one of my HD44780 displays use an inverted "P" instead of 
// a full block. Therefore a bar my look strange. Make the ASCII code
// of the full block configurable...
// done with the "Next Generation Layout"
// see the "asc255bug" attribute

// 2003-09-14 Markus <markus@norad.de>
// change %t tokens from Byte/sec to kB/sec, ith one decimal places. 
// Either make it configurabel, or add new tokens.
// done with the "Next Generation Layout"

// 2003-10-29 Matt Thrailkill <xwred1@modestolan.com>
// > To go off on another tangent... have you at all considered some sort of
// > marquee support?  I toyed with the row scrolling support which was
// > recently added, and it is nifty.  But marquees would be handy for doing
// > something like horizontally scrolling, say, the title of the currently
// > playing mp3.  I've toyed with trying to dive in and add it, but I'm a
// > pretty lazy guy and haven't done it.  What do you think?
// done with the "Next Generation Layout"

2003-12-31 Stefan ???  <nef17@gmx.net>
add support for software-controlled backlight for HD44780
http://www.jalcds.de/images/4x20backlight.gif

2004-01-25 Michael Reinelt <reinelt@eunet.at>
add attribute "blinking" to text widgets

2004-01-25 Xavier VELLO <xavier66@free.fr>
add "inverse" attribute to text widget
possible with Cwlinux and all graphics displays

2004-01-25 Xavier VELLO <xavier66@free.fr>
add an "image" widget

2004-01-25 Xavier VELLO <xavier66@free.fr>
icons should not only be updated regularly, but shown only when 
a certain expression returns 1