ChangeLogTag: Fri Nov 26 10:13:12 UTC 2004 Johnny Willemsen <jwillemsen@remedy.nl>

1 files changed, 26 insertions, 31 deletions

diff --git a/ACE-INSTALL.html b/ACE-INSTALL.html
index 2f9e372ce1d..948d7c9c232 100644
--- a/ACE-INSTALL.html
+++ b/ACE-INSTALL.html
@@ -15,7 +15,7 @@
 
 The file explains how to build and install ACE and its Network
 Services on the various OS platforms and compilers that it has been
-ported to.  Please consult the <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/ChangeLog">ChangeLog</a> file
+ported to.  Please consult the <a href="ChangeLog">ChangeLog</a> file
 to see whether any recent changes to the release will affect your
 code.  In addition, you should check out our <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/docs/ACE-development-process.html">development
 process</a>.  As you start working with ACE, we suggest you get copies
@@ -66,7 +66,7 @@ platforms is divided among a few different groups: the DOC group,
 Riverace, OCI, Remedy IT, and the ACE user community itself.  The
 table below summarizes each group's role and where you can get more
 detailed information.  For information on TAO's platform coverage and
-support, please also see <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/TAO/TAO-INSTALL.html">TAO's install
+support, please also see <a href="TAO/TAO-INSTALL.html">TAO's install
 document</a>.</p><p>
 
 <table border="1" width="75%">
@@ -102,7 +102,7 @@ document</a>.</p><p>
         software and service offerings.
     </td>
     <td>OCI's <a href="http://www.theaceorb.com/">web site</a> and
-        the TAO <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/TAO/TAO-INSTALL.html">install document</a></td>
+        the TAO <a href="TAO/TAO-INSTALL.html">install document</a></td>
   </tr>
   <tr>
     <th>Remedy IT</th>
@@ -113,7 +113,7 @@ document</a>.</p><p>
         HPUX 11i 32/64 bit on PA-RISC, and HPUX 11i v2 on Itanium.
     </td>
     <td>Remedy IT <a href="http://www.theaceorb.nl/">web site</a> and
-        the TAO <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/TAO/TAO-INSTALL.html">install document</a>
+        the TAO <a href="TAO/TAO-INSTALL.html">install document</a>
     </td>
   </tr>
   <tr>
@@ -169,9 +169,11 @@ of ACE (TAO and CIAO) includes GNUmakefiles for UNIX platforms, VC6
 project files, and VC71 solution files. If it is necessary to generate
 files for build tools for other compilers such as Visual Age for IBM,
 and Windows CE users have to run MPC themselves to generate the
-appropriate files. Please see <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/MPC/USAGE"> USAGE </a>, <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/MPC/README"> README </a> and <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/bin/MakeProjectCreator/README">README for ACE</a> files for
+appropriate files. Please see <a href="MPC/USAGE"> USAGE </a>, 
+<a href="MPC/README"> README </a> and 
+<a href="bin/MakeProjectCreator/README">README for ACE</a> files for
 details. The options that have been used to generate the above build
-files can be found in <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/bin/MakeProjectCreator/config/global.features">
+files can be found in <a href="bin/MakeProjectCreator/config/global.features">
 global.features</a> file.
 
 
@@ -274,7 +276,7 @@ global.features</a> file.
 
       Here's how to optimise the ACE library generation:</p><p>
 
-      Look at the <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/ace/GNUmakefile.ACE">ace/GNUmakefile.ACE</a>
+      Look at the <a href="ace/GNUmakefile.ACE">ace/GNUmakefile.ACE</a>
       in <code>$ACE_ROOT/ace</code>. Create a file called
       <code>ACE_All_Src.cpp</code>, and add a line to #include
       each of the source files
@@ -339,12 +341,6 @@ global.features</a> file.
             </pre><p>
       </p></li></ul>
 
-      With RedHat 5.0, you'll need some <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/os-patches/linux-patches.html">updates and possibly some
-      patches</a> to get ACE working with LinuxThreads.  Some of the
-      patches are necessary with Alpha CPUs and with some older
-      kernels.  egcs 1.0.1 can also be used, but it may need patches,
-      described there, as well.<p>
-
       <strong>NOTE:</strong> Be careful when installing egcs on RedHat
       systems.  If you don't remove your old gcc and libg++ RPMs, it's
       best to install egcs in a different directory than
@@ -561,9 +557,7 @@ global.features</a> file.
       &lt;<a href="mailto:levine@cs.wustl.edu">levine@cs.wustl.edu</a>&gt; has
       ported ACE to VxWorks 5.2/5.3/5.3.1/5.4 with the GreenHills
       1.8.8/1.8.9 and g++ compilers that are distributed with
-      VxWorks/Tornado.  An anonymous contributor has also
-      provided <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/os-patches/vxworks-5.1.txt">notes for using
-      ACE with VxWorks 5.1.</a>. It is not possible to use VxWorks 5.4
+      VxWorks/Tornado. It is not possible to use VxWorks 5.4
       and earlier with ACE anymore because the compilers delivered with
       5.4 and earlier don't support the C++ features ACE needs.</p><p>
 
@@ -626,7 +620,7 @@ global.features</a> file.
 
   </p></li><li><b>MVS OpenEdition</b> <p>
 
-      All of ACE has been ported to OpenEdition by Chuck Gehr &lt;<a href="mailto:gehr@sweng.stortek.com">gehr@sweng.stortek.com</a>&amp;gt.
+      All of ACE has been ported to OpenEdition by Chuck Gehr &lt;<a href="mailto:gehr@sweng.stortek.com">gehr@sweng.stortek.com</a>&gt;.
       The ACE library, all the tests and most of the examples and apps
       build clean.  There are still some problems that need to be
       ironed out:</p><p>
@@ -655,7 +649,7 @@ global.features</a> file.
       ACE has been ported to <a href="http://www.qnx.com/products/os/neutrino.html">QNX Neutrino
       2.0</a>.  We cross-compile for Neutrino on a QNX4 host using g++
       2.8.1, using the <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/ace/config-qnx-neutrino.h">ace/config-qnx-neutrino.h</a>
-      and <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/include/makeinclude/platform_qnx_neutrino.GNU">include/makeinclude/platform_qnx_neutrino.GNU</a>
+      and <a href="include/makeinclude/platform_qnx_neutrino.GNU">include/makeinclude/platform_qnx_neutrino.GNU</a>
       configuration files.  Many of the ACE tests succeed, though some
       fail.  As the porting effort progresses, we hope to eliminate
       these failures.  If you know of fixes, please send them to
@@ -960,7 +954,8 @@ your applications. The traditional configuration method is still more
 reliable. Any help you can
 lend to improve the ACE build process using GNU Autoconf would be very much
 appreciated. Please send any fixes to the
-<a href="mailto:ace-users@cs.wustl.edu">ACE users</a> mailing list.</p>
+<a href="mailto:ace-users@cs.wustl.edu">ACE users</a> mailing list
+using the standard <a href="PROBLEM-REPORT-FORM">problem-report-form</a>.</p>
 <p>
 The ACE only kit has been bootstrapped so you do not need to install
 the GNU Autotools (autoconf, automake, libtool) unless you want to
@@ -1137,13 +1132,13 @@ include $(ACE_ROOT)/include/makeinclude/platform_sunos5_sunc++.GNU
       library, tests, the examples, and the sample applications.
       Building the entire ACE release can take a long time and consume
       lots of disk space, however.  Therefore, you might consider
-      cd'ing into the <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/ace">$ACE_ROOT/ace/</a> directory and
+      cd'ing into the <a href="ace">$ACE_ROOT/ace/</a> directory and
       running <code>make</code> there to build just the ACE library.
       As a sanity check, you might also want to build and run the
-      automated <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/tests/README">"one-button" tests</a> in <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/tests/">$ACE_ROOT/tests/</a>.  Finally, if you're also
+      automated <a href="tests/README">"one-button" tests</a> in <a href="tests/">$ACE_ROOT/tests/</a>.  Finally, if you're also
       planning on building <a href="http://www.cs.wustl.edu/%7Eschmidt/TAO.html">TAO</a>, you
       should build the <a href="http://www.cs.wustl.edu/%7Eschmidt/PDF/gperf.pdf">gperf</a>
-      perfect hash function generator application in <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/apps/gperf">$ACE_ROOT/apps/gperf/</a>.</p><p>
+      perfect hash function generator application in <a href="apps/gperf">$ACE_ROOT/apps/gperf/</a>.</p><p>
 
   </p></li><li>If you need to regenerate the Svc_Conf_y.cpp file, you'll need to
       get <a href="http://ftp.gnu.org/pub/gnu/bison/">GNU Bison</a>.
@@ -1314,8 +1309,8 @@ Microsoft Visual C++</a></h4>
   files for static builds. Workspaces for static and DLL builds will be
   available through the stock release at DOC group's website. The
   workspaces for MFC are not available and have to be generated using
-  MPC. Please see <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/MPC/README">MPC's README</a> for
-  details.<br>
+  MPC. Please see <a href="MPC/README">MPC's README</a> for
+  details.<br><br>
   </li><li>Now load the workspace file for ACE (ACE_ROOT/ACE.dsw).<br>
       <br>
   </li><li>Make sure you are building the configuration (i.e, Debug/Release)
@@ -1388,7 +1383,7 @@ Microsoft Visual C++</a></h4>
 </li></ol>
 
 <p>More information for ACE/TAO on MSVC can be found
-<a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/docs/msvc_notes.txt">here</a>.  The doxygen version of this
+<a href="docs/msvc_notes.txt">here</a>.  The doxygen version of this
 document is available under Related Topics in the ACE Library.</p>
 
 <b>ACE TESTS</b><p>
@@ -1763,7 +1758,7 @@ for these notes):</p><p>
       downloaded and loaded into the VxWorks target system.<p>
   </p></li><li>C++ object modules must be post-processed by a VxWorks
       utility called "munch."  ACE includes a perl script called
-      <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/bin/ace_ld">$ACE_ROOT/bin/ace_ld</a>,
+      <a href="bin/ace_ld">$ACE_ROOT/bin/ace_ld</a>,
       which is called from the Makefiles, replacing
       the traditional <code>ld</code> step.  You must have perl installed
       to use <code>ace_ld</code>.  If perl is not on your path, you'll
@@ -2593,8 +2588,8 @@ ACE_Object_Manager</a></h4> The ACE_Object_Manager can be instantiated
 as a static object, can be instantiated on the stack of the main
 program thread, or can be explicitly instantiated and destroyed by the
 application with <code>ACE::init ()</code> and <code>ACE::fini
-()</code>.  The comments in the <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/ace/Object_Manager.h">header
-file, <code>ace/Object_Manager.h</code></a>, as well as Section 1.6.3 in
+()</code>.  The comments in the header file, 
+<a href="ace/Object_Manager.h"><code>ace/Object_Manager.h</code></a>, as well as Section 1.6.3 in
 <a href="http://www.riverace.com/docs">The ACE Programmer's Guide</a>
 provide more detail.<p>
 
@@ -2603,8 +2598,8 @@ Special requirements are imposed on applications if the
 ACE_Object_Manager is instantiated, by ACE, on the stack of the main
 thread.  This behavior is selected by defining
 <code>ACE_HAS_NONSTATIC_OBJECT_MANAGER</code> in
-<code>ace/config.h</code>.  Again, see the ACE Object_Manager <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/ace/Object_Manager.h">header file,
-<code>ace/Object_Manager.h</code></a> for more information.  One of
+<code>ace/config.h</code>.  Again, see the ACE Object_Manager header file,
+<a href="ace/Object_Manager.h"><code>ace/Object_Manager.h</code></a> for more information.  One of
 these requirements is discussed here, because it is so important.
 Please note that <code>ACE_HAS_NONSTATIC_OBJECT_MANAGER</code> is
 defined in the distributed ACE <code>config.h</code> headers for
@@ -2639,7 +2634,7 @@ entry point something other than <code>main</code>, you'll need to
 construct and destroy the ACE_Object_Manager.  The best way to do that
 is to call <code>ACE::init ()</code> and <code>ACE::fini ()</code>.
 Or, see the <code>#define</code> of <code>main (int, char *[])</code>
-in <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/ace/OS.h"><code>ace/OS.h</code></a> to see how ACE does
+in <a href="ace/OS_main.h"><code>ace/OS_main.h</code></a> to see how ACE does
 that for entry points named <code>main</code>.
 
 </p><p></p><hr align="left" width="50%"><p>