diff options
| -rw-r--r-- | ACE/ACE-INSTALL.html | 17 | ||||
| -rw-r--r-- | TAO/TAO-INSTALL.html | 19 |
2 files changed, 13 insertions, 23 deletions
diff --git a/ACE/ACE-INSTALL.html b/ACE/ACE-INSTALL.html index 0663ae72520..c9b8721a6af 100644 --- a/ACE/ACE-INSTALL.html +++ b/ACE/ACE-INSTALL.html @@ -463,8 +463,8 @@ State Perl.</a></p> Microsoft Visual Studio</a></h3> <p>ACE contains project files for -Visual Studio 2015 (vc14), and Visual Studio 2017 (vc141). -Visual Studio 2015 and 2017 use different file formats but the same file +Visual Studio 2015 (vc14), Visual Studio 2017 (vc141), and Visual Studio 2019 (vc142). +Visual Studio 2015/2017/2019 use different file formats but the same file suffixes (<code>.sln</code> and <code>.vcproj</code>). To support both environments, ACE supplies files with different names for the different development and target platforms. The platform/name mapping is shown below. @@ -489,6 +489,11 @@ a <code>.vcproj</code> suffix.</p> <td><i>name</i><code>_vs2017</code> </td> </tr> + <tr> + <th>Visual Studio 2019</th> + <td><i>name</i><code>_vs2019</code> + </td> + </tr> </tbody></table> <p>The VC++ compiler and linker can now be invoked from GNU make just like @@ -3092,18 +3097,16 @@ quickly. On Windows, with Visual Studio 2017, you must generate solution and project files with MPC:<p> <code> $ACE_ROOT/bin/mwc.pl -type vs2017 ACE.mwc </code> </p> + + On Windows, with Visual Studio 2019, you must generate solution and project files with MPC:<p> + <code> $ACE_ROOT/bin/mwc.pl -type vs2019 ACE.mwc </code> </p> </li><li>If you want to build TAO and its associated libraries please see <a href="TAO/TAO-INSTALL.html">TAO-INSTALL</a> for details. </li></ul> <hr><p> - Back to the <a href="https://www.dre.vanderbilt.edu/~schmidt/ACE.html">ACE</a> home page. - - - - </p><p> <!--<EM> Visitor # diff --git a/TAO/TAO-INSTALL.html b/TAO/TAO-INSTALL.html index e758e5f0a4f..c8fc3726cee 100644 --- a/TAO/TAO-INSTALL.html +++ b/TAO/TAO-INSTALL.html @@ -31,7 +31,7 @@ to run TAO on:<P> <table width="100%" border=1> <tr valign=top> <td><b>Fully supported, i.e., continually tested and used daily</b></td> - <td>Windows (Microsoft Visual C++ 7.1, 9.0, 10.0, 11.0, 12, 14.0, and 14.1), + <td>Windows (Microsoft Visual C++ 7.1, 9.0, 10.0, 11.0, 12, 14.0, 14.1, and 14.2), Linux/Intel (Redhat, Debian, and SuSe), Android </td> </tr> @@ -393,7 +393,7 @@ you need to have <code>TAO_IDL</code> compiled. <H4>Visual C++ 7.1 and newer</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++ 7.1 Project files +<CODE>ACE_wrappers\TAO</CODE> because the Visual Studio Project files are setup up to work in this configuration. If you move it, then make sure you regenerate the project files to look for the include and library files in the correct place. The default place for placing the @@ -409,7 +409,7 @@ project </a> file.</P> compiler under MSVC. If you intend to also use the release version of the libraries in the same workspace you have to be careful, since the executable name for TAO_IDL is same in debug - and release builds. You can use only or the oethr in the same + and release builds. You can use only or the other in the same workspace. This shouldn't be an issue since the projects for tests and examples are set up to transparently use one or the other. @@ -425,15 +425,6 @@ project </a> file.</P> and build both client and server. <P> </OL> -<H4>Visual C++ 7.0</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 above mentioned -points are also relevant to users who are trying to use TAO with VC++ -7.1. Additionally, all required options are set for the generated .sln -files. If something is missing then it is probably a bug with -MPC. Please report such bugs to the tao-users newsgroups. - <H4>Upgrading From Older Releases</H4> <P>When a newer version of ACE/TAO is installed, rebuild all should be @@ -472,10 +463,6 @@ The correct way is: execution of these tests. The scripts are found as "run_test.pl" in the directory of the test.</p> -<P> The versions of perl that we use are 5.005_02 on NT and 5.003 on Solaris. -The scripts may work on earlier versions of perl, but we cannot say for sure -that they do.</P> - <HR> <P> |