CHips L Pro sangad

Current Path : /proc/self/root/proc/self/root/usr/share/doc/cyrus-sasl-lib-2.1.23/

Current File : //proc/self/root/proc/self/root/usr/share/doc/cyrus-sasl-lib-2.1.23/advanced.html

<HTML><head>
<TITLE>Cyrus SASL Library -- Advanced Usage</TITLE>
</head>
<body>
<h1>Cyrus SASL library, version 2.0</h1>
<h2>Notes for Advanced Usage of libsasl</h2>

<h3>Using Cyrus SASL as a static library</h3>
As of v2.0.2-ALPHA, Cyrus SASL supports the option to compile all of the
supported mechanisms and glue code into a single static library that may
be linked into any application.  In practice, this saves memory by avoiding
the need to have a jump table for each process's reference into the shared
library, and ensures that all the mechanisms are loaded when the application
loads (thus reducing the overhead of loading the DSOs).<P>

However, this is not a recommended procedure to use in general.  It loses
the flexibility of the DSOs that allow one to simply drop in a new mechanism
that even currently-running applications will see for each new connection.
That is, if you choose to use the static version of the library, not only
will you need to recompile the library each time you add a mechanism (provided
the mechanisms even support being compiled staticly), but you will need to
recompile every application that uses Cyrus SASL as well.<P>

However, if you are sure you wish to use a static version of Cyrus SASL,
compile it by giving <tt>configure</tt> the <tt>--enable-static</tt> option.
This will compile <b>both</b> a dynamic and a static version.  Then, whenever
an application links to libsasl, it will also need to explicitly pull in
any dynamic libraries that may be needed by Cyrus SASL.  Most notably, these
might include the GSSAPI, Kerberos, and Database libraries.  To avoid compiling
the dynamic version, pass <tt>--disable-shared</tt>.<P>

<hr>
Back to the <A href=index.html>index</a>

</body>

CHips L MINI SHELL

CHips L pro