cd kalarm-1.4.13 ./configure make [ Log in as root ] cd /path/kalarm-1.4.13 make install
Options for ./configure which may be of particular use are:
--enable-doc-language=languages
Example: to install only British English documentation:
Example: to install only French, Spanish and Swedish documentation:
--prefix=kdedir
Example: to install into /opt/kde2:
WARNING: If you install into a different directory than the KDE installation, you must prefix your installation directory path to the run-time environment variable KDEDIRS, and restart KDE. Otherwise KAlarm will not run correctly. If you don't understand what this means, you should install into the standard KDE directory.
--disable-debug
Although KAlarm is a KDE application and requires the KDE libraries to be installed on your system, you can still use it while running other desktops or window managers.
In order to have alarms monitored and displayed automatically from one login
session to the next, the alarm daemon (which monitors the alarm list and tells
KAlarm to display each alarm when it becomes due) must be run automatically
when you graphically log in or otherwise start X. If you are running the KDE
desktop, the KAlarm installation process sets this up for you.
GNOME 2
Run Desktop Preferences -> Advanced -> Sessions. In the Sessions dialog,
select the Startup Programs tab and click Add. Enter kalarmd as the Startup
Command. This will run the alarm daemon every time you start up.
Depending on KAlarm's run mode (configurable in the Preferences dialog), you
may also need to run KAlarm at session start. If so, use the Startup Programs
tab to add kalarm --tray as an additional Startup Command.
Other Window Managers
If you can send me details on how to set up the daemon for any particular
window manager, I will include these in the next version of KAlarm.
If you want to use KAlarm with a non-KDE window manager, you have two alternatives:
kalarmd -session 117f000002000100176495700000008340018
You can use the ps command to check this.
kalarmd --autostart
If your desktop environment or window manager has a facility to configure programs to be run at login, you can use that facility. Otherwise, you need to add the command to an appropriate script which is run after X is started.
If you can specify an order to start the applications, start kalarm first, then kalarmd.
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:
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
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.
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). Specific --enable- and --with- options that the package recognises are described above in Quick Guide.
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 recognises the following options to control how it
operates.
--cache-file=file
--help
--quiet
--silent
-q
--srcdir=dir
--version