ChangeLogTag:Thu Jan 1 21:28:35 2004 Balachandran Natarajan <bala@dre.vanderbilt.edu>

1 files changed, 30 insertions, 5 deletions

diff --git a/TAO/TAO-INSTALL.html b/TAO/TAO-INSTALL.html
index 6918c48b4ea..12639898231 100644
--- a/TAO/TAO-INSTALL.html
+++ b/TAO/TAO-INSTALL.html
@@ -19,7 +19,7 @@
 <table width="100%" border=1>
   <tr valign=top>
     <td><b>Fully supported, i.e., continually tested and used daily</b></td>
-    <td>Solaris 2.5, 2.6, 7, and 8, Windows NT/2000/XP (MSVC 5.x, 6.x, and 7.x and
+    <td>Solaris 2.5, 2.6, 7, and 8, Windows NT/2000/XP (6.x, and 7.1 and
         Borland C++ Builder 4, 5, and 6), Linux/Intel, Linux/Alpha, VxWorks, LynxOS,
         Digital UNIX 4.0 and 5.0, IRIX 6.x, and QNX Neutrino 2.0
     </td>
@@ -303,16 +303,16 @@ in all cases.  </P>
 Remember to <a href="../ACE-INSTALL.html">set
 up ACE</A> before building TAO.
 
-<H4>Visual C++ 5.0/6.0</H4>
+<H4>Visual C++ 6.0</H4>
 
 <P>It works best if TAO is placed in ACE_wrappers so TAO ends up in
-<CODE>ACE_wrappers\TAO</CODE> because the Visual C++ 5/6 Project files
+<CODE>ACE_wrappers\TAO</CODE> because the Visual C++ 6 Project files
 are set up to work in this configuration. If you move it, then make
 sure you change the project files to look for the include and library
 files in the correct place.</P>
 
 <OL>
-  <LI>Make sure ACE is built (For Visual C++ 5.0/6.0, use ace.dsw). <P>
+  <LI>Make sure ACE is built (For Visual C++ 6.0, use ace.dsw). <P>
 
   <LI>First make sure <CODE>ACE_wrappers\bin</CODE> is listed in the Executable
       Directories in Tools|Options.  This is needed if using the TAO_IDL
@@ -334,7 +334,7 @@ files in the correct place.</P>
 
 <H4><A NAME="taoace">TAOACE.dsw and other collection dsw files</A></H4>
 
-<P>TAOACE.dsw is a Visual C++ 5.0/6.0 workspace that loads the projects
+<P>TAOACE.dsw is a Visual C++ 6.0 workspace that loads the projects
 ACE, TAO, TAO_IDL (the compiler), gperf, the orb services libraries, and
 the standalone executables (such as Naming Service, etc.).  It can be
 used to build all the files needed to build/run TAO applications.</P>
@@ -344,6 +344,31 @@ is generated by MPC, the DLLs will be placed in ACE_wrappers\lib instead
 of ACE_wrappers\bin.  So, you will need to ensure that %ACE_ROOT%\lib is
 in your PATH environment variable.</P>
 
+<H4>Visual C++ 7.1</H4>
+The DOC group doesn't support TAO on VC++ 7.0 since the libraries that
+were shipped with VC++ 7.0 did not work well. The DOC group supports
+only VC++ 7.1, which is used by their sponsors. The following points are
+relevant to users who are trying to use TAO with VC++ 7.1. 
+
+<P> Most of the information provided for VC++ 6.0 apply. But VC++ 7.1
+users cannot use the dsw files that are shipped with the
+distribution. There are multiple ways in which users can build TAO
+with VC++ 7.1</P>
+
+<OL>
+  <LI>Users can open up VC++ 6.0 projects within VC++7.1 environments.
+  VC++ 7.1 does a decent job, in our experience, of converting the
+  projects and workspace files into corresponding solution and
+  vcproj files that are usable in VC++ 7.1 environment. <P>
+
+  <LI>Another methodology is to use MPC to generate the solution
+  files. Please see the documentation of MPC in
+  ../bin/MakeProjectCreator/README for more information. The DOC group
+  doesn't plan to ship solution files for VC++ 7.1 projects since MPC is
+  very flexible and versatile. <P>
+  
+</OL>
+
 <H4>Borland C++ Builder</H4> <P>
 
 To build TAO using C++Builder please follow the