head 1.2;
access;
symbols
RPM_4_2_1:1.1.1.5
RPM_4_2:1.1.1.5
RPM_4_1_1:1.1.1.5
RPM_4_1:1.1.1.4
RPM_4_0_5:1.1.1.3
RPM_4_0_4:1.1.1.2
RPM_4_0_3:1.1.1.1
RPM:1.1.1;
locks; strict;
comment @# @;
1.2
date 2008.01.02.09.54.59; author rse; state dead;
branches;
next 1.1;
commitid z4cpSiAhOCXk5PLs;
1.1
date 2001.07.23.20.45.37; author rse; state Exp;
branches
1.1.1.1;
next ;
1.1.1.1
date 2001.07.23.20.45.37; author rse; state Exp;
branches;
next 1.1.1.2;
1.1.1.2
date 2002.01.08.00.30.11; author rse; state Exp;
branches;
next 1.1.1.3;
1.1.1.3
date 2003.01.18.13.49.02; author rse; state Exp;
branches;
next 1.1.1.4;
1.1.1.4
date 2001.12.06.00.08.15; author rse; state Exp;
branches;
next 1.1.1.5;
1.1.1.5
date 2003.01.18.14.04.59; author rse; state Exp;
branches;
next ;
desc
@@
1.2
log
@remove the ancient RPM 4.2.1 source tree copy
@
text
@
Berkeley DB Reference Guide: Running the test suite under Windows
- Berkeley DB Reference Guide:
- Building Berkeley DB for Windows systems
|
  
|
Running the test suite under Windows
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).
Building the software needed by the tests
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.
- Open the build_win32/Berkeley_DB.dsw workspace.
- Add the pathname for the Tcl include subdirectory to your
include path. To do this, under the Tools menu item, select
Options. In the dialog, select the Directories
tab, and choose directories for Include Files. Add
d:/tcl/include (or whatever directory contains tcl.h
in your distribution) to the list.
- Add the pathname for the Tcl library subdirectory to your
library path. To do this, under the Tools menu item, select
Options. In the dialog, select the Directories
tab, and choose directories for Library Files. Add
d:/tcl/lib (or whatever directory contains tcl83d.lib
in your distribution) to the list.
- Set the active configuration to db_test -- Debug. To set an
active configuration, under the Build menu item in the IDE,
select Set Active Configuration. Then choose
db_test -- Debug.
- Build. The IDE menu for this is called "build dbkill.exe",
even though dbkill is just one of the things that is built.
This step builds the base Berkeley DB .dll, tcl support,
and various tools that are needed by the test suite.
Running the test suite under Windows
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:
SET PATH=%PATH%;C:\db\build_win32\Debug\libdb_tcl32d.dll
Then, in a shell of your choice enter the following commands:
- cd build_win32
- run d:/tcl/bin/tclsh83d.exe, or the equivalent name of
the Tcl shell for your distribution.
You should get a "%" prompt.
- % source ../test/test.tcl.
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
@
1.1
log
@Initial revision
@
text
@d1 1
a1 1
@
1.1.1.1
log
@Import: RPM 4.0.3
@
text
@@
1.1.1.2
log
@Import: RPM 4.0.4
@
text
@d1 1
a1 1
d20 1
a20 1
and disk (around 250MB of disk will be sufficient).
d22 7
a54 3
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.
@
1.1.1.3
log
@Import: RPM 4.0.5
@
text
@d1 2
a2 2
a3 1
d22 3
a24 1
To build for testing, perform the following steps.
d27 20
a46 12
Build the Tcl API (see Building the Tcl API for details).
In Visual C++ 6.0, set the active configuration to db_test --
Debug. To set an active configuration, under the Build menu,
select Set Active Configuration. Then choose db_test
-- Debug. In Visual C++ .NET, just make sure Debug is
selected in the drop down list on the tool bar.
Build. In Visual C++ 6.0, the IDE menu item for this is called
"build dbkill.exe", even though dbkill is just one of the things that is
built. In Visual C++ .NET, right-click on the db_test project
and select Build. This step makes sure that the base Berkeley DB
.dll, tcl support, and various tools that are needed by the test suite are
all built.
d63 3
a65 5
path to Berkeley DB's tcl library is in your current path. On Windows NT/2000/XP,
edit your PATH using the My Computer -> Properties -> Advanced
-> Environment Variables dialog. On earlier versions of Windows, you
may find it convenient to add a line to c:\AUTOEXEC.BAT:
SET PATH=%PATH%;c:\db\build_win32\Debug
d73 1
a73 1
If no errors occur, you should get a "%" prompt.
@
1.1.1.4
log
@Import: RPM 4.1
@
text
@d1 2
a2 2
d4 1
d23 1
a23 3
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.
d26 12
a37 20
Add the pathname for the Tcl include subdirectory to your
include path. To do this, under the Tools menu item, select
Options. In the dialog, select the Directories
tab, and choose directories for Include Files. Add
d:/tcl/include (or whatever directory contains tcl.h
in your distribution) to the list.
Add the pathname for the Tcl library subdirectory to your
library path. To do this, under the Tools menu item, select
Options. In the dialog, select the Directories
tab, and choose directories for Library Files. Add
d:/tcl/lib (or whatever directory contains tcl83d.lib
in your distribution) to the list.
Set the active configuration to db_test -- Debug. To set an
active configuration, under the Build menu item in the IDE,
select Set Active Configuration. Then choose
db_test -- Debug.
Build. The IDE menu for this is called "build dbkill.exe",
even though dbkill is just one of the things that is built.
This step builds the base Berkeley DB .dll, tcl support,
and various tools that are needed by the test suite.
d54 5
a58 3
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:
SET PATH=%PATH%;C:\db\build_win32\Debug\libdb_tcl32d.dll
d66 1
a66 1
You should get a "%" prompt with no errors.
@
1.1.1.5
log
@Import: RPM 4.1.1
@
text
@d1 2
a2 2
a3 1
d22 3
a24 1
To build for testing, perform the following steps.
d27 20
a46 12
Build the Tcl API (see Building the Tcl API for details).
In Visual C++ 6.0, set the active configuration to db_test --
Debug. To set an active configuration, under the Build menu,
select Set Active Configuration. Then choose db_test
-- Debug. In Visual C++ .NET, just make sure Debug is
selected in the drop down list on the tool bar.
Build. In Visual C++ 6.0, the IDE menu item for this is called
"build dbkill.exe", even though dbkill is just one of the things that is
built. In Visual C++ .NET, right-click on the db_test project
and select Build. This step makes sure that the base Berkeley DB
.dll, tcl support, and various tools that are needed by the test suite are
all built.
d63 3
a65 5
path to Berkeley DB's tcl library is in your current path. On Windows NT/2000/XP,
edit your PATH using the My Computer -> Properties -> Advanced
-> Environment Variables dialog. On earlier versions of Windows, you
may find it convenient to add a line to c:\AUTOEXEC.BAT:
SET PATH=%PATH%;c:\db\build_win32\Debug
d73 1
a73 1
If no errors occur, you should get a "%" prompt.
@