Jan-Willem Neurdenburg
jotOmega dsc
56 Brigham Hill Road
Grafton MA 01519-1135
neurdenburgj@acm.org
Tel: (508) 839-0276
Fax: (508) 839-7267
Any other extensions that is compatible with Tcl release 8.0 can be used as well.
The root directory of the release contains the README files with installation instructions and the files needed to build and install this product. It also contains the executable scripts of the BlueGnu testing framework.
The top-level directories are listed below:
It also contains the TEX version (README.tex) of this document as well as the 'dvi', 'ps' 'html', and 'pdf' representation, respectively notice.dvi, notice.ps, notice.html, and notice.pdf.
Before you can install and use BlueGnu you need to have installed the following three packages:
The following examples use the command `./configure -prefix=/tools/...`. This will install all packages in a directory ``/tools''. When you omit the ``-prefix''-switch then the installation default will be the directory ``/usr/local''.
When you have not installed Tcl and the other needed extensions, then you need to retrieve the sources from ``www.tcltk.com/itcl''. You need to `gunzip` the files and do a `tar xf` of all these packages in one directory, let's call this directory ``TclTk''.
From the directory ``TclTk'', you should do the following to install the packages:
% cd tcl8.0.3/unix % ./configure --prefix=/tools/tcl8.0.3 --enable-gcc --enable-shared % make % mkdir /tools/tcl8.0.3 % make install % cd ../../tk8.0.3/unix % ./configure --prefix=/tools/tk8.0.3 --enable-gcc --enable-shared % make % mkdir /tools/tk8.0.3 % make install % cd ../../itcl3.0.1 % ./configure --prefix=/tools/itcl3.0.1 --enable-gcc --enable-shared % make % mkdir /tools/itcl3.0.1 % make install
% cd bluegnu2.0.3 % ./configure --prefix=/tools/bluegnu2.0.3 % make % mkdir /tools/bluegnu2.0.3 % make install
This will install BlueGnu in the directories:
% bluegnu versionTcl.itcl % bluegnu ts_001 % bluegnu ts_002 % bluegnu ts_003
The above test result should all be PASS. The following test will give a result UNKNOWN, because no pass/fail instruction have been given.
% bluegnu tc001
The last test you can run will fail in its simple form:
% bluegnu tc002
But will pass if you execute the test as follows:
% bluegnu tc002[English]
This is because the test scripts need a test case identifier to find the correct benchmark code.
_
001, ts_
002, and
ts_
003. The first two are not as easy to write as the
third. The test suite ts_
001 is a script implementation of the
command line:
% cd bluegnu2.0.3/testsets % bluegnu examples/tc002[English=B] \ > "examples/tc002[Dutch=B]={MSG=Hallo Wereld}"This may be useful for simple tests but when you want to write more complex test-suite scripts you would like some more flexibility, so two procedures were introduced, which are shown in test-suite ts
_
002. This
makes writing rather complex so the procedures have become part of
the procedures 'appendQueue', 'prependQueue', and 'runtest'. The
resulting script is shown in test-suit ts_
003.
Changes like this will be made in the future!
_
start', '<target>_
load', '<target>_
exit', and
'<target>_
version', which have been taken from DejaGnu.
This document was generated using the LaTeX2HTML translator Version 98.1p1 release (March 2nd, 1998)
Copyright © 1993, 1994, 1995, 1996, 1997, Nikos Drakos, Computer Based Learning Unit, University of Leeds.
The command line arguments were:
latex2html -t BlueGnu Release Notice -split 0 READMEdvi.tex.
The translation was initiated by Jan-Willem Neurdenburg on 1999-09-19