Index of /archives/NetBSD/NetBSD-release-9/src/external/bsd/openldap/dist/contrib/ldapc++
Name Last modified Size Description
Parent Directory -
AUTHORS 2008-05-22 23:20 32
COPYRIGHT 2019-08-10 15:17 234
CVS/ 2024-02-15 03:51 -
Makefile.am 2019-08-10 15:17 225
Makefile.in 2019-08-10 15:17 19K
README 2008-05-22 23:20 1.4K
TODO 2008-05-22 23:20 1.0K
aclocal.m4 2008-07-17 13:32 264K
config.guess 2017-02-01 18:26 43K
config.sub 2017-02-01 18:26 36K
configure 2019-08-10 15:17 665K
configure.in 2019-08-10 15:17 2.9K
depcomp 2008-05-22 23:20 16K
doxygen.rc 2014-05-28 18:58 54K
examples/ 2024-02-15 03:46 -
install-sh 2008-05-22 23:20 9.0K
ltmain.sh 2008-05-22 23:20 192K
missing 2008-05-22 23:20 11K
src/ 2024-02-15 03:46 -
version.sh 2019-08-10 15:17 351
version.var 2019-08-10 15:17 274
This is an unstable development release of a LDAPv3 C++ Class Library.
It was created as the diploma thesis (final project) of my computer
science studies.
It is based upon the OpenLDAP C-API and so it needs the C-library and
Headerfiles installed.
Installation:
=============
Just run the "configure" script with the apropriate options. Especially
these two options can be imported, if you didn't install the OpenLDAP-
libraries in the default place:
--with-libldap=<path to libldap> : To tell configure where the OpenLDAP
C-libraries are located.
--with-ldap-includes=<path to ldap include files> : To tell configure
where the OpenLDAP include files are located.
--enable-debug to enable compliation with debugging symbols and stderr
output
(run "configure --help" to see all possible command line options)
If configure finishes without problems. You can simply call "make" to
build the library and "make install" to install it.
Documentation:
==============
Docs are very incomplete. You can either look in the source files for
the documentation comment of generate documentation using "doxygen"
or any other javadoc compatible documentation generator.
Bugreports and other feedback:
==============================
If you find bugs please feel free to send me a detailed report. All
other kinds of feedback are welcomed as well.
Ralf Haferkamp <[email protected]>