There are several arguments you can specify when configuring Berkeley DB XML. Although only the Berkeley DB XML-specific ones are described here, most of the standard autoconf arguments are available and supported. To see a complete list of possible arguments, specify the --help flag to the configure program.
The Berkeley DB XML specific arguments are as follows:
--enable-debug
Use this flag to build with -g as a compiler
flag and with DEBUG defined during compilation. This will
create libraries and utilities with debugging
symbols. This argument should not be specified when
configuring to build production binaries.
--enable-java
To build the Berkeley DB XML Java API, enter --enable-java as an argument to configure. To build Java, you must also build with shared libraries. Before configuring, you must set your PATH environment variable to include javac. Note that it is not sufficient to include a symbolic link to javac in your PATH because the configuration process uses the location of javac to determine the location of the Java include files (for example, jni.h). On some systems, additional include directories may be needed to process jni.h; see Changing compilation and link options for more options.
--enable-perl
Use this flag to build with Perl support. This builds Perl support for both Berkeley DB and Berkeley DB XML. This option requires a working perl program in your PATH.
--enable-shared, --enable-static
On systems supporting shared libraries, Berkeley DB XML builds both static and shared libraries by default. (Shared libraries are built using the GNU Project's Libtool distribution, which supports shared library builds on many (although not all) systems.) To not build shared libraries, configure using the --enable-shared='no' argument. To not build static libraries, configure using the --enable-static='no' argument.
--enable-test
To build the Berkeley DB XML test suite, enter --enable-test as an argument to configure. To run the Berkeley DB XML test suite, you must also build the Tcl version of the Berkeley DB XML library by specifying--with-tcl=path. If Java is enabled and you use --enable-test you will also be required to supply the --with-junit flag (see below).
--with-junit
Path to the JUnit jar file, for example --with-junit=. This option is required if both --enable-test and -enable-java are specified.
--with-berkeleydb=DIR
To specify the location of a Berkeley DB installation to be used when building Berkeley DB XML, enter --with-berkeleydb=DIR, replacing DIR with the path to the top-level directory of the Berkeley DB installation.
--with-xerces=DIR
To specify the location of a Xerces installation to be used when building Berkeley DB XML, enter --with-xerces=DIR, replacing DIR with the path to the top-level directory of the Xerces installation.
--with-xqilla=DIR
To specify the location of a XQilla installation to be used when building Berkeley DB XML, enter --with-xqilla=DIR, replacing DIR with the path to the top-level directory of the XQilla installation.
--with-tcl=DIR
To build the Tcl version of the Berkeley DB XML
libraries, enter --with-tcl=DIR, replacing DIR with
the directory in which the Tcl tclConfig.sh file may
be found. See Loading Berkeley DB with Tcl in the Berkeley DB Programmer's Reference Guide
for information on sites from which you can download Tcl
and which Tcl versions are compatible with Berkeley
DB XML. To build Tcl, you must also build with
shared libraries.