OSB/OpenVXI Build Instructions

 

 

 

1. Third Party Software:

 

All third party software must be downloaded the compiled prior to building OpenVXI 3.0. Build instructions are provided in the third party software distribution package. The OpenVXI team has only tested/built with the versions listed below, we highly recommend that you use these versions. The OpenVXI source code may need to be modified to work with different versions, problems with different versions may include build errors or robustness issues.

 

 

2. Linux

 

* Requirements:

- gcc version 3.2.2 or later

- Xerces Version 2.3.0

- SpiderMonkey 1.5rc5

- Perl 5.6 or later

* Environment variables:

The following environment variables must be set prior of building

OpenVXI 3.0 sources.

- SWISBSDK points to the baseline of OpenVXI 3.0 for the build environment

†† The baseline structure must be created as following:

†† $(SWISBSDK)/bin, $(SWISBSDK)/lib, $(SWISBSDK)/include, $(SWISBSDK)/config

- XERCESDIR points to the root directory of pre-compiled Xerces 2.3

- SPIDERMONKEYDIR points to the root directory of pre-compiled SpiderMonkey 1.5rc5

* Build and Build order:

To build OpenVXI 3.0 sources, cd to each component in the order outlined below, and carry out the following commands: gmake or gmake all to build, gmake clean to clean.

After a successful build, all relevant files will be appropriately copied to the baseline.

By default debug libraries are built, specify CFG=release or CFG=debug on the gmake command line to explicitly choose which build type to produce.

To ensure a successful build, the following order must be followed:

cd $SWISBSDK/lib

- VXIinterfaces

- swichar

- trd

- value

- log

- cache

- inet

- VXI

 

3. Windows

* Requirements:

- MSVC++ 6.0

- Xerces Version 2.3.0

- SpiderMonkey 1.5rc5

- OpenSSL 0.9.7b

- Perl 5.6 or later

- A third party STL library (MSVCís STL has known robustness and threading problems, we do not recommend using that STL library. The dsp files may need to be modified to build with your STL library of choice, by default MSVCís STL library will be used. The OpenVXI team internally tests with a commercial STL library, we are looking into testing with an open source STL library for future builds).

* Environment variables:

The following environment variables must be set prior of building

OpenVXI 3.0 sources.

- SWISBSDK points to the baseline of OpenVXI 3.0 for the build environment.

†† The baseline structure must be created as following:

†† $(SWISBSDK)\bin, $(SWISBSDK)\lib, $(SWISBSDK)\include, $(SWISBSDK)\config

- XERCESDIR points to the root directory of pre-compiled Xerces 2.3.0

- SPIDERMONKEYDIR points to the root directory of pre-compiled SpiderMonkey 1.5rc5

- OPENSSLDIR points to the root directory of pre-compiled OpenSSL 0.9.7b

* Build and Build order:

To build OpenVXI 3.0 sources, navigate to each component directory in order outlined below and open the necessary dsp file(s). Navigate to Build menu, select Batch Build then check the appropriate build mode, then click Rebuild All.

After a successful build, all relevant files will be appropriately copied to the baseline

To ensure a successful build, the following order must be followed (there may be multiple dsp files in each directory, make sure you build everything):

 

- VXIinterfaces

- swichar

- trd

- value

- log

- cache

- inet

- VXI

4. Other OS Build instructions

 

OpenVXI does not explicitly support or test with other OSís at this time. If an integrator would like to support another OS we would recommend starting with the Linux build instructions and Makefiles as a base. From time to time we have incorporated changes integrators have done to support other OSís when practical. Please post any OS related changes to the Open VXI mailing list (vxi-discuss@speechinfo.org) for consideration in future versions of OpenVXI.