intro.so

berkeley db 4.6.21的源码。berkeley db是一个简单的数据库管理系统

m4_section([Building the C++ API])
m4_p([dnl
C++ support is built automatically on Windows.])

m4_section([Building the Java API])
m4_p([dnl
Java support is not built automatically.  The following instructions
assume that you have installed the Sun Java Development Kit in
m4_path(d:\java).  Of course, if you installed elsewhere or have
different Java software, you will need to adjust the pathnames
accordingly.])

m4_subsection([Building Java with Visual C++ .NET or above])

m4_nlistbegin

m4_nlist([dnl
Set your include directories.  Choose m4_italic([Tools -__GT__ Options
-__GT__ Projects -__GT__ VC++ Directories]).  Under the "Show
directories for" pull-down, select "Include files".  Add the full
pathnames for the m4_path(d:\java\include) and
m4_path(d:\java\include\win32) directories.  Then click OK.  These are
the directories needed when including jni.h.])

m4_nlist([dnl
Set the executable files directories.  Choose m4_italic([Tools -__GT__
Options -__GT__ Projects -__GT__ VC++ Directories]).  Under the "Show
directories for" pull-down, select "Executable files".  Add the full
pathname for the m4_path(d:\java\bin) directory, then click OK.  This is
the directory needed to find javac.])

m4_nlist([dnl
Set the build type to Release or Debug in the drop-down on the .NET
tool bar.])

m4_nlist([dnl
To build, right-click on db_java and select Build.  This builds the
Java support library for m4_db and compiles all the java files,
placing the resulting m4_path(db.jar) and m4_path(dbexamples.jar)
files in the m4_path(build_windows\Release) or
m4_path(build_windows\Debug) subdirectory of m4_db.])

m4_nlistend

m4_subsection([Building Java with Visual C++ 6.0])

m4_nlistbegin

m4_nlist([dnl
Set the include directories.  Choose m4_italic([Tools -__GT__ Options
-__GT__ Directories]).  Under the "Show directories for" pull-down,
select "Include files".  Add the full pathnames for the
m4_path(d:\java\include) and m4_path(d:\java\include\win32) directories.
These are the directories needed when including m4_path(jni.h).])

m4_nlist([dnl
Set the executable files directories.  Choose m4_italic([Tools -__GT__
Options -__GT__ Directories]).  Under the "Show directories for"
pull-down, select "Executable files".  Add the full pathname for the
m4_path(d:\java\bin) directory.  This is the directory needed to find
javac.])

m4_nlist([dnl
Go to m4_italic([Build -__GT__ Set Active Configuration]) and select
either the Debug or Release version of the db_java project.  Then
press OK.])

m4_nlist([dnl
To build, select m4_italic([Build -__GT__ Build
libdb_java[]M4MAJOR[]M4MINOR.dll]).  This builds the Java support
library for m4_db and compiles all the java files, placing the
resulting m4_path(db.jar) and m4_path(dbexamples.jar) files in the
m4_path(build_windows\Release) or m4_path(build_windows\Debug)
subdirectory of m4_db.])

m4_nlistend

m4_p([dnl
To run Java code, set your environment variable m4_envvar(CLASSPATH)
to include the full pathname of these jar files, and your environment
variable m4_envvar(PATH) to include the m4_path(build_windows\Release)
subdirectory.  On Windows, remember that files or directories in the
m4_envvar(CLASSPATH) and m4_envvar(PATH) variables must be separated
by semicolons (unlike UNIX).  Then, try running the following command
as a test:])

m4_indent([java db.AccessExample])

m4_p([dnl
If you want to run Java code using a Debug build, substitute 'Debug'
for 'Release' in the instructions above.  Make sure you use the Debug
JAR file with the Debug DLL and the Release JAR with the Release
DLL.])

m4_section([Building the Tcl API])
m4_p([dnl
Tcl support is not built automatically.  See
m4_link(M4RELDIR/ref/tcl/intro, Loading m4_db with Tcl) for
information on sites from which you can download Tcl and which Tcl
versions are compatible with m4_db.  These notes assume that Tcl is
installed as m4_path(d:\tcl), but you can change that if you want.])

m4_p([dnl
The Tcl library must be built as the same build type as the m4_db
library (both Release or both Debug).  We found that the binary
release of Tcl can be used with the Release configuration of m4_db,
but you will need to build Tcl from sources for the Debug
configuration.  Before building Tcl, you will need to modify its
makefile to make sure that 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 m4_db.])

m4_subsection([Building Tcl with Visual C++ .NET or above])

m4_nlistbegin

m4_nlist([dnl
Set the include directories.  Choose m4_italic([Tools -__GT__ Options
-__GT__ Projects -__GT__ VC++ Directories]).  Under the "Show
directories for" pull-down, select "Include files".  Add the full
pathname for m4_path(d:\tcl\include), then click OK.  This is the
directory that contains m4_path(tcl.h).])

m4_nlist([dnl
Set the library files directory.  Choose m4_italic([Tools -__GT__
Options -__GT__ Projects -__GT__ VC++ Directories]).  Under the "Show
directories for" pull-down, select "Library files".  Add the full
pathname for the m4_path(d:\tcl\lib) directory, then click OK.  This is
the directory needed to find
m4_path(tcl[]TCLMAJOR[]TCLMINOR[]TCLDEBUG.lib) (or whatever the
library is named in your distribution).])

m4_nlist([dnl
Set the build type to Release or Debug in the drop-down on the .NET
tool bar.])

m4_nlist([dnl
To build, right-click on db_tcl and select Build.  This builds the Tcl
support library for m4_db, placing the result into
m4_path(build_windows\Debug\libdb_tcl[]M4MAJOR[]M4MINOR[]d.dll) or
m4_path(build_windows\Release\libdb_tcl[]M4MAJOR[]M4MINOR.dll).])

m4_nlistend

m4_p([dnl
If you use a version different from Tcl TCLMAJOR.TCLMINOR.x you will
need to change the name of the Tcl library used in the build (for
example, m4_path(tcl[]TCLMAJOR[]TCLMINOR[]TCLDEBUG.lib)) to the
appropriate name.  To do this, right click on m4_italic(db_tcl), go to
m4_italic([Properties -__GT__ Linker -__GT__ Input -__GT__ Additional
dependencies]) and change
m4_path(tcl[]TCLMAJOR[]TCLMINOR[]TCLDEBUG.lib) to match the Tcl
version you are using.])

m4_subsection([Building Tcl with Visual C++ 6.0])

m4_nlistbegin

m4_nlist([dnl
Set the include directories.  Choose m4_italic([Tools -__GT__ Options
-__GT__ Directories]).  Under the "Show directories for" pull-down,
select "Include files".  Add the full pathname for
m4_path(d:\tcl\include), then click OK.  This is the directory that
contains m4_path(tcl.h).])

m4_nlist([dnl
Set the library files directory.  Choose m4_italic([Tools -__GT__
Options -__GT__ Directories]).  Under the "Show directories for"
pull-down, select "Library files".  Add the full pathname for the
m4_path(d:\tcl\lib) directory, then click OK.  This is the directory
needed to find m4_path(tcl[]TCLMAJOR[]TCLMINOR[]TCLDEBUG.lib) (or
whatever the library is named in your distribution).])

m4_nlist([dnl
Go to m4_italic([Build -__GT__ Set Active Configuration]) and select
either the Debug or Release version of the db_tcl project.  Then press
OK.])

m4_nlist([dnl
To build, select m4_italic([Build -__GT__ Build
libdb_tcl[]M4MAJOR[]M4MINOR.dll]).  This builds the Tcl support
library for m4_db, placing the result into
m4_path(build_windows\Debug\libdb_tcl[]M4MAJOR[]M4MINOR[]d.dll) or
m4_path(build_windows\Release\libdb_tcl[]M4MAJOR[]M4MINOR.dll).])

m4_nlistend

m4_p([dnl
If you use a version different from Tcl TCLMAJOR.TCLMINOR.x you will
need to change the name of the Tcl library used in the build (for
example, m4_path(tcl[]TCLMAJOR[]TCLMINOR[]TCLDEBUG.lib)) to the
appropriate name.  To do this, choose
m4_italic([Project -__GT__ Settings -__GT__ db_tcl])
and change the Tcl library listed in the Object/Library modules
m4_path(tcl[]TCLMAJOR[]TCLMINOR[]TCLDEBUG.lib) to match the Tcl version
you are using.])

m4_section([Distributing DLLs])
m4_p([dnl
When distributing applications linked against the DLL (not static)
version of the library, the DLL files you need will be found in the
m4_path(build_windows\Release) subdirectory, or
m4_path(build_windows\Debug) if you distribute a debug version.  You may
also need to redistribute DLL files needed for the compiler's runtime.
For Visual C++ 6.0, these files are m4_path(msvcrt.dll) and
m4_path(msvcp60.dll) if you built with a Release configuration, or
m4_path(msvcrtd.dll) and m4_path(msvcp60d.dll) if you are using a
Debug configuration.  Generally, these runtime DLL files can be
installed in the same directory that will contain your installed m4_db
DLLs.  This directory may need to be added to your System PATH
environment variable.  Check your compiler's license and documentation
for specifics on redistributing runtime DLLs.])

m4_page_footer