diff options
Diffstat (limited to 'bdb/docs/ref/build_win')
| -rw-r--r-- | bdb/docs/ref/build_win/faq.html | 49 | ||||
| -rw-r--r-- | bdb/docs/ref/build_win/intro.html | 143 | ||||
| -rw-r--r-- | bdb/docs/ref/build_win/notes.html | 56 | ||||
| -rw-r--r-- | bdb/docs/ref/build_win/test.html | 77 |
4 files changed, 0 insertions, 325 deletions
diff --git a/bdb/docs/ref/build_win/faq.html b/bdb/docs/ref/build_win/faq.html deleted file mode 100644 index 2c185b6daa2..00000000000 --- a/bdb/docs/ref/build_win/faq.html +++ /dev/null @@ -1,49 +0,0 @@ -<!--$Id: faq.so,v 10.20 2000/06/28 15:43:27 bostic Exp $--> -<!--Copyright 1997, 1998, 1999, 2000 by Sleepycat Software, Inc.--> -<!--All rights reserved.--> -<html> -<head> -<title>Berkeley DB Reference Guide: Windows FAQ</title> -<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit."> -<meta name="keywords" content="embedded,database,programmatic,toolkit,b+tree,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,java,C,C++"> -</head> -<body bgcolor=white> - <a name="2"><!--meow--></a> <a name="3"><!--meow--></a> -<table><tr valign=top> -<td><h3><dl><dt>Berkeley DB Reference Guide:<dd>Building Berkeley DB for Windows systems</dl></h3></td> -<td width="1%"><a href="../../ref/build_win/notes.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../../ref/toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../../ref/build_vxworks/intro.html"><img src="../../images/next.gif" alt="Next"></a> -</td></tr></table> -<p> -<h1 align=center>Windows FAQ</h1> -<p><ol> -<p><li><b>My Win* C/C++ application crashes in the Berkeley DB library when Berkeley DB calls -fprintf (or some other standard C library function).</b> -<p>You should be using the "Debug Multithreaded DLL" compiler option in -your application when you link with the -build_win32/Debug/libdb32d.lib library (this .lib file -is actually a stub for libdb32d.DLL). To check this -setting in Visual C++, choose the "Project/Settings" menu item, and -under the tab marked "C/C++", select "Code Generation" and see the box -marked "Use runtime library". This should be set to "Debug -Multithreaded DLL". If your application is linked against the static -library, build_win32/Debug/libdb32sd.lib, then you -will want to set "Use runtime library" to "Debug Multithreaded". -<p>Setting this option incorrectly can cause multiple versions of the -standard libraries to be linked into your application (one on behalf -of your application, and one on behalf of the Berkeley DB library). That -violates assumptions made by these libraries, and traps can result. -<p><li><b>Why are the build options for DB_DLL marked as "Use MFC in a Shared DLL"? -Does Berkeley DB use MFC?</b> -<p>Berkeley DB does not use MFC at all. It does however, call malloc and free and -other facilities provided by the Microsoft C runtime library. We've found -in our work that many applications and libraries are built assuming MFC, -and specifying this for Berkeley DB solves various interoperation issues, and -guarantees that the right runtime libraries are selected. Note that since -we do not use MFC facilities, the MFC library DLL is not marked as a -dependency for libdb.dll, but the appropriate Microsoft C runtime is. -</ol> -<table><tr><td><br></td><td width="1%"><a href="../../ref/build_win/notes.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../../ref/toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../../ref/build_vxworks/intro.html"><img src="../../images/next.gif" alt="Next"></a> -</td></tr></table> -<p><font size=1><a href="http://www.sleepycat.com">Copyright Sleepycat Software</a></font> -</body> -</html> diff --git a/bdb/docs/ref/build_win/intro.html b/bdb/docs/ref/build_win/intro.html deleted file mode 100644 index 6f5e0d4bbf4..00000000000 --- a/bdb/docs/ref/build_win/intro.html +++ /dev/null @@ -1,143 +0,0 @@ -<!--"@(#)intro.so 10.26 (Sleepycat) 11/18/99"--> -<!--Copyright 1997, 1998, 1999, 2000 by Sleepycat Software, Inc.--> -<!--All rights reserved.--> -<html> -<head> -<title>Berkeley DB Reference Guide: Building for Win32</title> -<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit."> -<meta name="keywords" content="embedded,database,programmatic,toolkit,b+tree,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,java,C,C++"> -</head> -<body bgcolor=white> - <a name="2"><!--meow--></a> -<table><tr valign=top> -<td><h3><dl><dt>Berkeley DB Reference Guide:<dd>Building Berkeley DB for Win32 platforms</dl></h3></td> -<td width="1%"><a href="../../ref/build_unix/ultrix.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../../ref/toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../../ref/build_win/test.html"><img src="../../images/next.gif" alt="Next"></a> -</td></tr></table> -<p> -<h1 align=center>Building for Win32</h1> -<p>The build_win32 directory in the Berkeley DB distribution contains project files -for both MSVC 5.0 and 6.0: -<p><table border=1 align=center> -<tr><th>Project File</th><th>Description</th></tr> -<tr> <td align=center>Berkeley_DB.dsw</td> <td align=center>Visual C++ 5.0 project (compatible with 6.0)</td> </tr> -<tr> <td align=center>*.dsp</td> <td align=center>Visual C++ 5.0 subprojects (compatible with 6.0 -)</td> </tr> -</table> -<p>These project files can be used to build Berkeley DB for any Win32 platform: -Windows 2000, Windows NT, Windows 98 and Windows 95. -<h3>Building With Visual C++ 6.0</h3> -<p>Open the file <b>Berkeley_DB.dsw</b>. You will be told that the project -was generated by a previous version of Developer Studio, and asked if you -want to convert the project. Select Yes, and all projects will be -converted. Then continue on with the instructions for building with -Visual C++ 5.0. -<p>Note that when you build a release version, you may receive a warning -about an unknown compiler option <i>/Ob2</i>. This is apparently a -flaw in the project conversion for Visual C++ and can be ignored. -<p>Each release of Berkeley DB is built and tested with this procedure using -Microsoft Visual C++ 6.0, Standard Edition. -<h3>Building With Visual C++ 5.0</h3> -<p>Open the file <b>Berkeley_DB.dsw</b>. This workspace includes a number -of subprojects needed to build Berkeley DB. -<p>First, you'll need to set the include directories. To do this, select -<i>Options...</i> from the <i>Tools</i> pull-down menu. At this -point, a tabbed dialogue should appear. In this new window, choose the -<i>Directories</i> tab. For the <i>Platform</i>, select -<i>Win32</i> and for <i>Show directories for</i> select -<i>Include files</i>. Below these options in the list of directories, -you should add two directories: the full pathname of the -<i>build_win32</i> subdirectory of Berkeley DB, followed by the full -pathname of the <i>include</i> subdirectory of Berkeley DB. Then click OK. -<p>Then, select <i>Active Project Configuration</i> under the -<i>Build</i> pull-down menu. For a debug version of the libraries, -tools and examples, select <i>db_buildall - Win32 Debug</i>. -Results from this build are put into <b>build_win32/Debug</b>. -For a release version, select <i>db_buildall - Win32 Release</i>; -results are put into <b>build_win32/Release</b>. -For a debug version that has all tools and examples built with -static libraries, select <i>db_buildall - Win32 Debug Static</i>; -results are put into <b>build_win32/Debug_static</b>. -For a release version of the same, -select <i>db_buildall - Win32 Release Static</i>; -results are put into <b>build_win32/Release_static</b>. -Finally, to build, select <i>Build db_buildall.exe</i> under the -<i>Build</i> pull-down menu. -<p>When building your application, you should normally use compile options -"debug multithreaded dll" and link against -<b>build_win32/Debug/libdb32d.lib</b>. If you want -to link against a static (non-DLL) version of the library, use the -"debug multithreaded" compile options and link against -<b>build_win32/Debug_static/libdb32sd.lib</b>. You can -also build using a release version of the libraries and tools, which will be -placed in <b>build_win32/Release/libdb32.lib</b>. -The static version will be in -<b>build_win32/Release_static/libdb32s.lib</b>. -<p>Each release of Berkeley DB is maintained, built and tested using Microsoft -Visual C++ 5.0 and 6.0. -<h3>Including the C++ API</h3> -<p>C++ support is built automatically on Win32. -<h3>Including the Java API</h3> -<p>Java support is not built automatically. The following instructions -assume you have installed the Sun Java Development Kit in -<b>d:/java</b>. Of course, if you've installed elsewhere, or have -different Java software, you will need to adjust the pathnames -accordingly. First, use the instructions above for Visual C++ 5.0 or 6.0 -to open the Tools/Options tabbed dialog for adding include directories. -In addition to the directories specified above, add -<b>d:/java/include</b> and <b>d:/java/include/win32</b>. These are -the directories needed when including <b>jni.h</b>. Now, before -clicking OK, under <i>Show directories for</i>, choose -<i>Executable files</i>. Add <b>d:/java/bin</b>. That directory -is needed to find javac. Now select OK. -<p>Select <i>Active Project Configuration</i> under the -<i>Build</i> pull-down menu. Choose <i>db_java - Win32 -Release</i>. To build, select <i>Build -libdb_java32.dll</i> under the <i>Build</i> pull-down -menu. This builds the Java support library for Berkeley DB and compiles all -the java files, placing the class files in the <b>java/classes</b> -subdirectory of Berkeley DB. Set your environment variable CLASSPATH to -include this directory, your environment variable PATH to include the -<b>build_win32/Release</b> subdirectory, and as a test, try running -the command: -<p><blockquote><pre>java com.sleepycat.examples.AccessExample</pre></blockquote> -<h3>Including the Tcl API</h3> -<p>Tcl support is not built automatically. See -<a href="../../ref/tcl/intro.html">Loading Berkeley DB with Tcl</a> for information -on sites from which you can download Tcl and which Tcl versions are -compatible with Berkeley DB. -<p>The Tcl library must be built as the same build type as the Berkeley DB -library (both Release or both Debug). We have found that the binary -release of Tcl can be used with the Release configuration of Berkeley DB, but -for the Debug configuration, you will need to need to build Tcl from -sources. Before building Tcl, you will need to modify its makefile to -make sure you are building a debug version, including thread support. -This is because the set of DLLs linked into the Tcl executable must -match the corresponding set of DLLs used by Berkeley DB. -<p>These notes assume Tcl is installed as <b>d:/tcl</b>, but you can -change that if you wish. If you run using a different version of Tcl -than the one currently being used by Sleepycat Software, you will need -to change the name of the Tcl library used in the build (e.g., -tcl83d.lib) to the appropriate name. See -Projects->Settings->Link in the db_tcl subproject. -<p>Use the instructions above for -Visual C++ 5.0 or 6.0 to open the <i>Tools/Options</i> tabbed dialog -for adding include directories. In addition to the directories specified -above, add <b>d:/tcl/include</b>. This is the directory that contains -<b>tcl.h</b>. -Then, in that same dialog, show directories for "Library Files". -Add <b>d:/tcl/lib</b> (or whatever directory contains -<b>tcl83d.lib</b> in your distribution) to the list. Now select OK. -<p>Select <i>Active Project Configuration</i> under the -<i>Build</i> pull-down menu. Choose <i>db_tcl - Win32 -Release</i>. To build, select <i>Build -libdb_tcl32.dll</i> under the <i>Build</i> pull-down -menu. This builds the Tcl support library for Berkeley DB, placing the result -into <b>build_win32/Release/libdb_tcl32.dll</b>. -Selecting an Active Configuration of <i>db_tcl - Win32 Debug</i> -will build a debug version, placing the result into -<b>build_win32/Debug/libdb_tcl32d.dll</b>. -<table><tr><td><br></td><td width="1%"><a href="../../ref/build_unix/ultrix.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../../ref/toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../../ref/build_win/test.html"><img src="../../images/next.gif" alt="Next"></a> -</td></tr></table> -<p><font size=1><a href="http://www.sleepycat.com">Copyright Sleepycat Software</a></font> -</body> -</html> diff --git a/bdb/docs/ref/build_win/notes.html b/bdb/docs/ref/build_win/notes.html deleted file mode 100644 index 483b101ecc2..00000000000 --- a/bdb/docs/ref/build_win/notes.html +++ /dev/null @@ -1,56 +0,0 @@ -<!--$Id: notes.so,v 10.17 2000/11/02 16:46:11 bostic Exp $--> -<!--Copyright 1997, 1998, 1999, 2000 by Sleepycat Software, Inc.--> -<!--All rights reserved.--> -<html> -<head> -<title>Berkeley DB Reference Guide: Windows notes</title> -<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit."> -<meta name="keywords" content="embedded,database,programmatic,toolkit,b+tree,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,java,C,C++"> -</head> -<body bgcolor=white> - <a name="2"><!--meow--></a> -<table><tr valign=top> -<td><h3><dl><dt>Berkeley DB Reference Guide:<dd>Building Berkeley DB for Windows systems</dl></h3></td> -<td width="1%"><a href="../../ref/build_win/test.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../../ref/toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../../ref/build_win/faq.html"><img src="../../images/next.gif" alt="Next"></a> -</td></tr></table> -<p> -<h1 align=center>Windows notes</h1> -<ul type=disc> -<li>Various Berkeley DB interfaces take a <b>mode</b> argument, intended to specify -the underlying file permissions for created files. Berkeley DB currently ignores -this argument on Windows systems. -<p>It would be possible to construct a set of security attributes to pass to -<b>CreateFile</b> that accurately represents the mode. In the worst -case, this would involve looking up user and all group names and creating -an entry for each. Alternatively, we could call the <b>_chmod</b> -(partial emulation) function after file creation, although this leaves us -with an obvious race. -<p>Practically speaking, however, these efforts would be largely meaningless -on FAT, the most common file system, which only has a "readable" and -"writeable" flag, applying to all users. -<li>When using the <a href="../../api_c/env_open.html#DB_SYSTEM_MEM">DB_SYSTEM_MEM</a> flag, Berkeley DB shared regions are -created without ACLs, which means that the regions are only accessible -to a single user. If wider sharing is appropriate (e.g., both user -applications and Windows/NT service applications need to access the -Berkeley DB regions), the Berkeley DB code will need to be modified to create the -shared regions with the correct ACLs. Alternatively, by not specifying -the <a href="../../api_c/env_open.html#DB_SYSTEM_MEM">DB_SYSTEM_MEM</a> flag, file-system backed regions will be -created instead, and the permissions on those files may be directly -specified through the <a href="../../api_c/env_open.html">DBENV->open</a> interface. -<li>On Windows/9X, files opened by multiple processes do not share data -correctly. For this reason, the <a href="../../api_c/env_open.html#DB_SYSTEM_MEM">DB_SYSTEM_MEM</a> flag is implied -for any application that does not specify the <a href="../../api_c/env_open.html#DB_PRIVATE">DB_PRIVATE</a> flag, -causing the system paging file to be used for sharing data. However, -paging file memory is freed on last close, implying that multiple -processes sharing an environment must arrange for at least one process -to always have the environment open, or, alternatively, that any process -joining the environment be prepared to re-create it. If a shared -environment is closed by all processes, a subsequent open without -specifying the <a href="../../api_c/env_open.html#DB_CREATE">DB_CREATE</a> flag will result in the return of a -system EAGAIN error code. -</ul> -<table><tr><td><br></td><td width="1%"><a href="../../ref/build_win/test.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../../ref/toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../../ref/build_win/faq.html"><img src="../../images/next.gif" alt="Next"></a> -</td></tr></table> -<p><font size=1><a href="http://www.sleepycat.com">Copyright Sleepycat Software</a></font> -</body> -</html> diff --git a/bdb/docs/ref/build_win/test.html b/bdb/docs/ref/build_win/test.html deleted file mode 100644 index e3230ca84a4..00000000000 --- a/bdb/docs/ref/build_win/test.html +++ /dev/null @@ -1,77 +0,0 @@ -<!--$Id: test.so,v 10.29 2001/01/17 14:42:57 bostic Exp $--> -<!--Copyright 1997, 1998, 1999, 2000 by Sleepycat Software, Inc.--> -<!--All rights reserved.--> -<html> -<head> -<title>Berkeley DB Reference Guide: Running the test suite under Windows</title> -<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit."> -<meta name="keywords" content="embedded,database,programmatic,toolkit,b+tree,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,java,C,C++"> -</head> -<body bgcolor=white> - <a name="2"><!--meow--></a> <a name="3"><!--meow--></a> -<table><tr valign=top> -<td><h3><dl><dt>Berkeley DB Reference Guide:<dd>Building Berkeley DB for Windows systems</dl></h3></td> -<td width="1%"><a href="../../ref/build_win/intro.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../../ref/toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../../ref/build_win/notes.html"><img src="../../images/next.gif" alt="Next"></a> -</td></tr></table> -<p> -<h1 align=center>Running the test suite under Windows</h1> -<p>To build the test suite on Win32 platforms you will need to configure -Tcl support. You will also need sufficient main memory and disk. -Something around 100MB of disk will be sufficient. For memory, 32MB is -too small, we recommend at least 64MB. -<h3>Building the software needed by the tests</h3> -<p>There exist 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. -<p>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. -<p><ol> -<p><li>Open the <b>build_win32/Berkeley_DB.dsw</b> workspace. -<p><li>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 <b>d:/tcl/include</b> (or whatever directory -contains <b>tcl.h</b> in your distribution) to the list. -<p><li>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 <b>d:/tcl/lib</b> (or whatever directory contains -<b>tcl83d.lib</b> in your distribution) to the list. -<p><li>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". -<p><li>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. -</ol> -<h3>Running the test suite under Windows</h3> -<p>Before running the tests for the first time, you must edit the file -<b>include.tcl</b> in your build directory and change the line -that reads: -<p><blockquote><pre>set tclsh_path SET_YOUR_TCLSH_PATH</pre></blockquote> -<p>You will want to use the location of the <b>tclsh</b> program. For -example, if Tcl is installed as <b>d:/tcl</b>, this line should be: -<p><blockquote><pre>set tclsh_path d:/tcl/bin/tclsh83d.exe</pre></blockquote> -<p>Then, in a shell of your choice enter the following commands: -<p><ol> -<p><li>cd build_win32 -<p><li>run <b>d:/tcl/bin/tclsh83d.exe</b>, or the equivalent name of -the Tcl shell for your distribution. -<p>You should get a "%" prompt. -<p><li>% source ../test/test.tcl. -<p>You should get a "%" prompt with no errors. -</ol> -<p>You are now ready to run tests in the test suite, see -<a href="../../ref/test/run.html">Running the test suite</a> for more -information. -<table><tr><td><br></td><td width="1%"><a href="../../ref/build_win/intro.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../../ref/toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../../ref/build_win/notes.html"><img src="../../images/next.gif" alt="Next"></a> -</td></tr></table> -<p><font size=1><a href="http://www.sleepycat.com">Copyright Sleepycat Software</a></font> -</body> -</html> |