RE: backend modules

["Howard Chu" <hyc@highlandsun.com>]

> From: Ben Collins [mailto:bmc@visi.net]On Behalf Of Ben Collins
> On Sat, Aug 07, 1999 at 02:46:33AM -0700, Howard Chu wrote:
> > OK. I've tested out static and dynamic builds for all of the
> backends except
> > bdb2. The install rules now use $libexecdir/$ldap_subdir for
> installing the
> > dynamic backends. I originally set up the build with libltdl
> copied into the
> > OpenLDAP source tree, but that was a real pain to get
> configured properly.
> > Now I just rely on libltdl already being installed on default
> search paths.
> > It seems this is OK since we already require libtool 1.3.3 to
> be installed
> > on the build system.
>
> No, libtool is not a requirement for compiling the source.
>
> Run libtoolize --help and you will see an option to make it copy
> libltdl into the source tree. Then just add these into configure.in
>
> dnl Must come before the other libtool macros
> AC_LIBLTDL_CONVENIENCE
> AC_LIBTOOL_DLOPEN
> AM_PROG_LIBTOOL
> AC_CONFIG_SUBDIRS(libltdl)
> .....
> AC_SUBST(LIBLTDL)
> CPPFLAGS="$CPPFLAGS $INCLTDL"
>
> Then @LIBTLDL@ should be added to the list of libs that slapd links
> against. This gives the configure script several options, a) use the
> included libltdl, b) use a version already installed on the system.
>
> Ben

I already went down this route. I did all the steps you outlined, but
there's more to it than you think, and it got ugly very quickly. Also,
we already decided that it's better not to include the ltdl source in
the OpenLDAP tree. The configuration that I finally checked in is much
cleaner.