1# $Id: README,v 12.0 2004/11/17 03:44:46 bostic Exp $ 2 3Use the scripts testall or testone to run all, or just one of the C++ 4tests. You must be in this directory to run them. For example, 5 6 $ export LIBS="-L/usr/include/BerkeleyDB/lib" 7 $ export CXXFLAGS="-I/usr/include/BerkeleyDB/include" 8 $ export LD_LIBRARY_PATH="/usr/include/BerkeleyDB/lib" 9 $ ./testone TestAppendRecno 10 $ ./testall 11 12The scripts will use c++ in your path. Set environment variables $CXX 13to override this. It will also honor any $CXXFLAGS and $LIBS 14variables that are set, except that -c are silently removed from 15$CXXFLAGS (since we do the compilation in one step). 16 17To run successfully, you will probably need to set $LD_LIBRARY_PATH 18to be the directory containing libdb_cxx-X.Y.so 19 20As an alternative, use the --prefix=<DIR> option, a la configure 21to set the top of the BerkeleyDB install directory. This forces 22the proper options to be added to $LIBS, $CXXFLAGS $LD_LIBRARY_PATH. 23For example, 24 25 $ ./testone --prefix=/usr/include/BerkeleyDB TestAppendRecno 26 $ ./testall --prefix=/usr/include/BerkeleyDB 27 28The test framework is pretty simple. Any <name>.cpp file in this 29directory that is not mentioned in the 'ignore' file represents a 30test. If the test is not compiled successfully, the compiler output 31is left in <name>.compileout . Otherwise, the java program is run in 32a clean subdirectory using as input <name>.testin, or if that doesn't 33exist, /dev/null. Output and error from the test run are put into 34<name>.out, <name>.err . If <name>.testout, <name>.testerr exist, 35they are used as reference files and any differences are reported. 36If either of the reference files does not exist, /dev/null is used. 37