To build the test suite on Win32 platforms, you will need to configure Tcl support. You will also need sufficient main memory (at least 64MB), and disk (around 100MB of disk will be sufficient).
There are bugs in some versions of Tcl that may cause the test suite to hang on Windows/NT 4.0. Tcl version 8.4 (currently available as an alpha release) has fixed the problem, or there are patches available for Tcl 8.3.2 (see bug #119188 in the Tcl SourceForge database). Note that if you want to run the test suite against a Debug version of Berkeley DB, you need to build a Debug version of Tcl. This involves building Tcl from its source.
To build, perform the following steps. Note that steps #1, #4, and #5 are part of the normal build process for building Berkeley DB; #2, #3 are part of including the Tcl API.
Before running the tests for the first time, you must edit the file include.tcl in your build directory and change the line that reads:
set tclsh_path SET_YOUR_TCLSH_PATH
You will want to use the location of the tclsh program (be sure to include the name of the executable). For example, if Tcl is installed in d:/tcl, this line should be the following:
set tclsh_path d:/tcl/bin/tclsh83d.exe
If your path includes spaces be sure to enclose it in quotes:
set tclsh_path "c:/Program Files/tcl/bin/tclsh83d.exe"
If you run the test suite from the command prompt make sure that the path to Berkeley DB's tcl library is in your current path. You may find it convenient to add a line to C:\AUTOEXEC.BAT:
Then, in a shell of your choice enter the following commands:
You should get a "%" prompt.
You should get a "%" prompt with no errors.
You are now ready to run tests in the test suite; see Running the test suite for more information.
Copyright Sleepycat Software