

In order to compile all of the programs included with this distribution you will
need to download, build, and install the following libraries and utilities.

1.   CppUnit from sourceforge (http://cppunit.sourceforge.net/)

     My development and testing machines have version 1.8.0 installed.

     CppUnit is an excellent regression testing framework used by the sca_test program.

     The library provides the user with the ability to define a virtually unlimited number
     of test cases that can be easily re-run during development to ensure that changes to
     code don't break prior dependencies.

2.   Statistics::Lite perl module (perl -MCPAN -e 'install Statistics::Lite')

     This perl module is used by a simple perl script that I wrote for analyzing the
     results from the sca_latency_test program.

     The perl module will perform simple mean, min, max, range, and standard deviation
     calculations when provided with an array of raw data.

     The perl script I wrote analyzes the raw data from the sca_latency_test program
     and prepares files that are appropriate for plotting with gnuplot.

3.   gnuplot (http://sourceforge.net/projects/gnuplot/)

     The graphs used in my analysis were prepared using gnuplot 3.7.1.

     More recent versions of gnuplot are available from sourceforge.net and should
     be compatible with the plot files and scripts generated for my data analysis.

4.   The Boost C++ library (http://www.boost.org)

     The sca_latency_test program uses a progress display to show the percentage of
     testing that has been completed so the user can have some sort of visual
     indication that the tests are running (i.e.:  not hanging).

5.   The JUnit testing framework (http://junit.sourceforge.net)

     The JUnit testing framework from [SOURCE OF JUNIT] is used to provide a way of
     running a common test suite against both the Java and C++ implementations of the SCA.

Compatible ORBS

     The SCA was developed primarily using MICO 2.3.8 on RedHat 7.1.  The following ORBs
     and operating systems were also used for testing.

       MICO 2.3.7   (Linux, Solaris 2.8)
       MICO 2.3.8   (Linux, Solaris 2.8)
       Orbix 2000   (Linux, Solaris 2.8)
       ACE+TAO 1.3  (Linux, Solaris 2.8, Windows 2000 Server)

     In order to add support for additional orbs down the road the developer should only need to add
     an appropriate section to the ./configure.in script.  The required modifications are well documented
     in that file.  You will need to gather the full path to the idl compiler along with the
     its required command line switches, the full path to the ORBs include directory, and the full
     path to the ORBS lib directories (along with the names for the libraries that contain the
     CosNaming and PortableServer code).
