We recommend that you download and build a distribution from Oracle. Some problems have been reported with linking to Debian, Cygwin or other packages. This is especially true for Windows users.
Beyond ensuring that the file “my-config.sexp” points to your BDB installation directories and files, nothing else should be required to configure the example that uses a local “testdb” directory as a dabase (under “tests”) in the top-level Elephant directory.
On one Fedora based system, the “my-config.sexp” file looked like this:
((:berkeley-db-include-dir . "/usr/local/BerkeleyDB.4.5/include") (:berkeley-db-lib-dir . "/usr/local/BerkeleyDB.4.5/lib") (:berkeley-db-lib . "/usr/local/BerkeleyDB.4.5/lib/libdb.so") (:berkeley-db-deadlock . "/usr/local/BerkeleyDB.4.5/bin/db_deadlock") (:pthread-lib . nil) (:clsql-lib . "/usr/local/share/common-lisp/") (:compiler . :gcc))
The Test Suites give a nice example of using BDB by running the test using the specification:
Once you start working on an application, you will want to change the
path to a directory that is appropriate for your application, and use
that as the specification passed to
open-store on application