<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content=
- "text/html; charset=utf-8" />
+ "text/html; charset=us-ascii" />
<title>INSTALL</title>
- <meta name="generator" content="Bluefish 1.0.7"/>
- <!-- $Id: INSTALL.html,v 1.8 2008/08/07 22:40:49 mrsam Exp $ -->
- <!-- Copyright 2004 Double Precision, Inc. See COPYING for -->
+ <!-- Copyright 2004-2012 Double Precision, Inc. See COPYING for -->
<!-- distribution information. -->
</head>
"http://www.gnu.org/software/binutils/">http://www.gnu.org/software/binutils/</a>)</li>
<li>Libtool (<a onclick="" href=
- "http://www.gnu.org/software/libtool/">http://www.gnu.org/software/libtool/</a>)</li>
+ "http://www.gnu.org/software/libtool/">http://www.gnu.org/software/libtool/</a>).
+ Additional, libtool's <tt>libltdl</tt> library, and its
+ development files, must be installed. On some platforms this is
+ a separate package. On Fedora, this is the
+ <tt>libtool-ltdl-devel</tt> package, for example.</li>
<li>GNU make (<a onclick="" href=
"http://www.gnu.org/software/make/">http://www.gnu.org/software/make/</a>)</li>
</ul>
<p>Courier-authlib uses Libtool to build shared libraries.
- Libtool is not strictly required, but Libtool should be installed
- unless a good -- a very-very good -- reason exists not to. If
- Libtool is not installed, a copy of Libtool in courier-authlib's
- source will be used. However, this may cause problems later down
- the road, if either another Libtool-using package is installed
- later, or if Libtool itself is installed. Bottom line: install
- Libtool.</p>
+ Libtool must be installed, together with its <tt>libltdl</tt>
+ library and its header files.</p>
<p>On non-Linux platforms the GNU linker is also required.
Courier-authlib's build script uses some GNU linker-specific
is used to provide LDAP services, OpenLDAP is still required to
enable LDAP services in Courier.</li>
- <li><strong>MySQL/PostgreSQL</strong> - The MySQL and
- PostgreSQL authentication modules require, obviously,
- MySQL/PostgreSQL development libraries.<br /></li>
+ <li><strong>MySQL</strong>, <strong>PostgreSQL</strong>, and
+ <strong>SQLite</strong> - The MySQL, PostgreSQL, and SQLite
+ authentication modules require, obviously,
+ MySQL/PostgreSQL/SQLite development libraries.<br /></li>
</ul>
<h2><a name="What" id="What">What gets installed</a></h2>
<p>RPM will refuse to build the Courier authentication library
unless all prerequisite development libraries for LDAP, MySQL,
- and PostgreSQL are installed. <strong>Do not try to hack the
- RPM build script to ignore these dependencies!</strong> For
- simplicity's and maintainability sake the RPM build script
- creates all available authentication modules. All extra
- authentication modules will be built as <em>optional</em>
- subpackages. They do not have to be installed at runtime.
- Install the LDAP, MySQL, and PostgreSQL development libraries
- only for the duration of building binary RPMs. They can be
- uninstalled afterwards.</p>
+ PostgreSQL, and SQLite are installed. <strong>Do not try to
+ hack the RPM build script to ignore these
+ dependencies!</strong> For simplicity's and maintainability
+ sake the RPM build script creates all available authentication
+ modules. All extra authentication modules will be built as
+ <em>optional</em> subpackages. They do not have to be installed
+ at runtime. Install the LDAP, MySQL, PostgreSQL, and SQLite
+ development libraries only for the duration of building binary
+ RPMs. They can be uninstalled afterwards.</p>
</blockquote>
<h2><a name="Guidelines" id="Guidelines">Guidelines for using
<li><code>%libdir%/courier-authlib/libauthmysql*</code> goes
into the MySQL subpackage.</li>
+ <li><code>%libdir%/courier-authlib/libauthsqlite*</code> goes
+ into the SQLite subpackage.</li>
+
<li><code>%libdir%/courier-authlib/libauthpgsql*</code> goes
into the PostgreSQL subpackage.</li>