Berkeley DB Reference Guide: Building Berkeley DB XML for UNIX/POSIX systems

Configuring Berkeley DB XML

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 GNU 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

To build Berkeley DB XML with -g as a compiler flag and with DEBUG #defined during compilation, enter --enable-debug as an argument to configure. This will create a Berkeley DB XML library and utilities with debugging symbols. This argument should not be specified when configuring to build production binaries.

--enable-diagnostic

To build Berkeley DB XML with run-time debugging checks, enter --enable-diagnostic as an argument to configure. This will cause a number of special checks to be performed when Berkeley DB XML is running. Applications built using this argument should not share database environments with applications built without this argument. 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 compile or load options for more information.

--disable-shared, --disable-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 --disable-shared argument. To not build static libraries, configure using the --disable-static 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. This argument should not be specified when configuring to build production binaries.

--enable-umrw

Rational Software's Purify product and other run-time tools complain about uninitialized reads/writes of structure fields whose only purpose is padding, as well as when heap memory that was never initialized is written to disk. Specify the --enable-umrw argument during configuration to mask these errors. This argument should not be specified when configuring to build production binaries.

--with-berkeleydb=DIR

To specify the location of a Berkeley DB distribution 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 distribution.

--with-xerces=DIR

To specify the location of a Xerces distribution 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 distribution.

--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 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.

Copyright (c) 1996-2003 Sleepycat Software, Inc. - All rights reserved.