11-Aug-2006
-----------
This file is out of date, env variables have been changed!

21-Oct-2005
-----------
To use this Visual Studio .NET 2003 solution, you must first set some environmental
variables.

o Right-click "My Computer"
o Choose "Properties"
o Click on the "Advanced" tab
o Push the "Environmental Variables" button
o In the "User variables for ..." pane, use the "New" button to create:
	CIPRES_CVS_ROOT -> the directory that *contains* the framework directory
    OMNIORB_TOP -> where you installed OmniORB (e.g. C:\omniORB-4.0.6)
	BOOST_ROOT -> where you installed Boost (the directory that contains a subdirectory
	named boost)
	PHYCAS_ROOT -> the directory that contains cipres_services (this isn't strictly needed
	for building libcipres but is needed for building phycas services).
o Navigate to $(CIPRES_CVS_ROOT)\framework\C++\build\VC7 and double-click
	the VC7.sln file
o When Visual Studio is finished loading, choose View > Solution Explorer
	if necessary to bring up the Solution Explorer
o Right-click the VC7 project in Solution Explorer and choose "Build"
	to build the library

31-Jan-2006
------------
We have a script in the IDL directory named compile.py that runs the idl compiler to generate .cpp and .h 
files in C++/CipresIDL if any of the .idl files have changed.  Previously we did this as a pre-build event
but the VC compiler was failing to compile the generated .cpp files the first time it was run.

The way I'm trying it now there's a custom build step for each of the .idl files that invokes compile.py.  
All of the generated .cpp and .h files are specified as "outputs" of the custom build step since
compile.py may create all of them anytime it's run.