From 7f7f9fb7d462bf13619c8610db902ae3fe2e1fb0 Mon Sep 17 00:00:00 2001
From: levine <levine@ae88bc3d-4319-0410-8dbf-d08b4c9d3795>
Date: Thu, 22 Jul 1999 15:43:19 +0000
Subject: ChangeLogTag: Thu Jul 22 10:42:06 1999  Clarence M. Weaver 
 <clarence_m_weaver@md.northgrum.com>

---
 ACE-INSTALL.html | 27 +++++++++++++++++----------
 1 file changed, 17 insertions(+), 10 deletions(-)

(limited to 'ACE-INSTALL.html')

diff --git a/ACE-INSTALL.html b/ACE-INSTALL.html
index 899b61fda62..c3979514306 100644
--- a/ACE-INSTALL.html
+++ b/ACE-INSTALL.html
@@ -753,7 +753,7 @@ If you use the GNU GCC g++ compiler please note the following:
       for reporting the problem with ACE_Singleton on g++, and for
       helping to find and implement these solutions.<P>
 
-  <LI>On VxWorks only, g++ (thru version 2.7.2, at least, distributed
+  <LI>On VxWorks only, g++ (thru version 2.7.2, distributed
       with Tornado 1.0.1/VxWorks 5.3.1), -fno-implicit-templates is
       broken.  In addition, -O2 is not supported on some targets.<P>
 </UL>
@@ -1263,15 +1263,22 @@ spa ace_main, "arg1" [, ...]
 
 All arguments must be quoted, even numbers.<p>
 
-By default, the ACE Makefiles link the ACE library into every
-executable.  If you want to run multiple ACE executables but just use
-a single ACE library, it should be possible, though I haven't tried
-it.  Just link the first executable to be loaded onto the target with
-the ACE library, as usual.  All other executables can be linked
-without the ACE library by added <code>ACELIB=</code> to the make
-invocation when building them.  When they are loaded onto the target,
-the should load against the symbols from the ACE library from the
-first executable that was loaded.<p>
+The ACE <a href="tests/">tests</a> write their output files in a
+directory named <code>log/</code>, below the current
+(<code>tests</code>) directory.  If you don't have NFS included in
+your VxWorks kernel, you can use these steps, provided by
+<a href="mailto:clarence_m_weaver@md.northgrum.com">Clarence M. Weaver</a>,
+to run the tests and capture their output:<p>
+<ol>
+  <li>What I did was create a log directory on the boot NT host of my vxworks
+    target.<p>
+  <li>I copied all the test applications and the run_tests.vxworks script to
+    the parent of the log directory.<p>
+  <li>Using the target shell not the host shell, I "cd" to the directory
+    containing the script and test programs.<p>
+  <li>Invoked the script &lt; run_tests.vxworks from this target shell.<p>
+</ol>
+
 
 <h5><a name="VxWorks/SharedLibs">Building Shared Libraries for VxWorks</a>.</h5>
 
-- 
cgit v1.2.1