How to compile POP3Lite
=======================

Its really quite simple --  its about the same difficulty as compiling
any GNU software.

	o Run `configure' by using one (and only one) of the following:

		./configure
		sh configure

	o By default, `configure' sets  up the software to be run from
	/usr/local -- if this is not the case for you (ie, you are not
	the  superuser compiling for  the entire  system) you  can run
	configure  with  the  `--prefix=/path/to/somewhere' flag,  for
	example:

		./configure --prefix=/home/users/pop3

	o POP3Lite's build infrastructure fully supports all the bells
	and  whistles   that  configure  provides   for  compiling  in
	different  places  and  for  different systems  and  all  that
	esoteric stuff only used by package maintainers.

	o There are several options supported by our configure script:

	  --enable-debugging
	  	POP3Lite will  try to log debug  messages, however, if
		you want  to see  this messages, you  have to  set the
		MINIMUM_LOG_LEVEL variable to 0 in pop3lite.conf.
	  --with-modules=[LIST]
		A coma separated list  of modules that should be built
	  	as loadable.
	  --with-disabled-modules=[LIST]
		A coma  separated list of  modules that should  not be
	  	built at all.
	  --with-builtin-modules=[LIST]
	    	A coma separated list  of modules that should be built
		into  the daemon  itself.
	  --with-layout=[LAYOUT]
		Use a predefined directory layout for installation.

	For more information, see the output of `./configure --help'.

	o This  POP3Lite daemon should be  able to compile  and run on
        almost any modern  Unix (A `modern' Unix is  one that supports
        POSIX system calls and BSD  networking in addition to the most
        commonly accepted non-standard  Unix extensions, like getpw*()
        functions.)  All I can say is  try it and see if it works.  It
        will definitely work on FreeBSD, GNU/Linux, GNU/Hurd, etc.

	o To compile  POP3Lite,  type `make'.   This will  compile the
	`pop3lite' program in the  `src' subdirectory, and the various
	modules in their own subdirectories.

	o Once  that  you  are  happy with  the  compilation, you  can
	install them  with `make install'.  This will  install all the
	binaries, and scripts into  the path specified in the Makefile
	(or when you ran configure).

	o You can now delete the object files and binaries if you want
	to save  some space by typing  `make clean'.  If  you are sure
	you probably wont have to  compile again, but you want to keep
	the  source code around,  you can  use `make  distclean'.  You
	should make  distclean before you  try to compile again  for a
	different architecture.

	o Bug  reports  go to  8@free.bsd.hu. Please  include  as much
	information as possible.

How to compile POP3Lite statically
==================================

	o Run `configure'  with the `--enable-static-daemon' flag. For
	example:

		./configure --enable-static-daemon

	o If  you  want  a  really  static   daemon,  you  should  run
	`configure' with the `--disable-module-support' option.

	o Follow the steps above