Updates for R3.14.1.

2002-11-22 20:20:48 +00:00
parent f81bff13fa
commit 40e6553dcc
6 changed files with 13 additions and 67 deletions
@@ -10,12 +10,12 @@
 <body>

 <center>
-<h2>Building EPICS R3.13 applications with R3.14.0beta2 base</h2>
+<h2>Building EPICS R3.13 applications with R3.14.1 base</h2>
 </center>

 <p><br>
 This document describes how to modify a R3.13 vxWorks application so that it
-builds with release R3.14.0beta2.  It describes an easy way to modify
+builds with release R3.14.1.  It describes an easy way to modify
 applications subject to the following restrictions:</p>
 <ul>
  <li>The application still uses config rules rather than the configure rules
@@ -69,7 +69,7 @@ however, has a config directory. Makesure that config/RELEASE has the same
 location for base as configure/RELEASE.</p>

 <p>snc is no longer in base. If snc is used in your application, you must
-download and build the seq module with baseR3.14.0beta2. See the Application
+download and build the seq module with baseR3.14.1. See the Application
 Developer's Guide to see how to build sequence programs.</p>

 <p>If you build sequencer programs add the lines</p>
@@ -9,7 +9,7 @@
 <body>

 <center>
-<h2>Building EPICS R3.13 extensions with R3.14.0beta2 base</h2>
+<h2>Building EPICS R3.13 extensions with R3.14.1 base</h2>
 </center>

 <p><br>
@@ -10,12 +10,12 @@
 <body>

 <center>
-<h2>Converting an EPICS R3.13 application to R3.14.0.beta2</h2>
+<h2>Converting an EPICS R3.13 application to R3.14.1</h2>
 </center>

 <p><br>
 This document describes how to convert a R3.13 vxWorks application so that it
-builds with release R3.14.0beta2.  It describes procedures such that:</p>
+builds with release R3.14.1.  It describes procedures such that:</p>
 <ul>
  <li>The application uses the configure rules which are new to R3.14.</li>
 </ul>
@@ -49,7 +49,7 @@ If sequence programs (*.st or *.stt files) exist in your application, add the
 SNCSEQ location definition for the R3.14 seq external module</p>

 <p><tt>SNCSEQ =&lt;full path to seq module top&gt;</tt></p>
-The R3.14 seq module must exist and be built with EPICS base R3.14.0beta2
+The R3.14 seq module must exist and be built with EPICS base R3.14.1

 <h3>Modify the Makefiles in &lt;top&gt;/*App directories.</h3>

@@ -9,62 +9,8 @@
 </head>

 <body>
-<h1 style="text-align: center">EPICS base R3.14.0beta2: Known Problems</h1>
+<h1 style="text-align: center">EPICS base R3.14.1: Known Problems</h1>

-<h2>vxWorks TIMEZONE pentium</h2>

-<p>If the name of the timezone has more than a few characters a crash can
-occur on pentium vxWorks iocs. See ansiTime in the vxWorks reference manual
-for details about TIMEZONE.</p>
+</p><h3>No known problems.</h3>

-<h2>GNU make version</h2>
-
-<p>GNU make version 3.78.1 or later is required for builds. The README.html
-file specifies version 3.70 but this version does not support the call
-function.</p>
-
-<h2>Borland build</h2>
-
-<p>The borland-x86 build of base fails in src/ca because the Borland compiler
-v5.5 does not support C++ placement delete. A fix is to add the following
-code after the #include lines in ca/netIO.h and ca/syncGroup.h.</p>
-
-<blockquote>
-  <code>// does the local compiler support placement delete</code><br />
-  <code>#if defined (_MSC_VER)</code><br />
-  <code># if _MSC_VER &gt;= 1200</code><br />
-  <code># define NETIO_PLACEMENT_DELETE</code><br />
-  <code># endif</code><br />
-  <code>#elif defined ( __HP_aCC )</code><br />
-  <code># if _HP_aCC &gt; 033300</code><br />
-  <code># define NETIO_PLACEMENT_DELETE</code><br />
-  <code># endif</code><br />
-  <code>#elif defined ( __BORLANDC__ )</code><br />
-  <code># if __BORLANDC__ &gt; 0x550</code><br />
-  <code># define NETIO_PLACEMENT_DELETE</code><br />
-  <code># endif</code><br />
-  <code>#else</code><br />
-  <code># define NETIO_PLACEMENT_DELETE</code><br />
-  <code>#endif</code><br />
-</blockquote>
-
-<h2>Visual C++ 6.0 Build</h2>
-
-<p>The order of certain Microsoft header file includes must be rearranged as
-follows in base/src/osi/os/win32/osdMutex.c and possibly also
-base/src/libCom/osi/os/win32/osdEvent.c. This problem does not exist with
-Visual C++ 7.0 (visual C++ .net).</p>
-
-<p><code>// visual c++ 6.0 appears to be sensitive to the</code></p>
-
-<p><code>// order of the following four lines</code></p>
-
-<p><code>#define VC_EXTRALEAN</code></p>
-
-<p><code>#define _WIN32_WINNT 0x400</code> </p>
-
-<p><code>#include &lt;windows.h&gt;</code></p>
-
-<p><code>#include &lt;winsock2.h&gt;</code></p>
-</body>
-</html>
@@ -4,7 +4,7 @@ README

                           EPICS base

-                      Release 3.14.0beta2
+                      Release 3.14.1

 What is EPICS base?

@@ -408,7 +408,7 @@ Example application and extension
     Instructions for building and executing the 3.14 example application
     can be found in the section "Example Application" of Chapter 2, "New
     Features for 3.14", in the  "IOC Application Developer's Guide
-     R3.14.0beta2". The "Example Application" section briefly explains
+     R3.14.1". The "Example Application" section briefly explains
     how to create and build an example application in a user created <top>
     directory. It also explains how to run the example application on a
     vxWorks ioc or a host system and run an example channel access client
@@ -17,7 +17,7 @@ EPICS base</h2></center>

 <center>
 <h2>
-Release 3.14.0beta2</h2></center>
+Release 3.14.1</h2></center>

 <h3>
 What is EPICS base?</h3>
@@ -531,7 +531,7 @@ during the base build.</blockquote>

 <blockquote>Instructions for building and executing the 3.14 example application
 can be found in the section "Example Application" of Chapter 2, "New Features
-for 3.14", in the "IOC Application Developer's Guide R3.14.0beta2".
+for 3.14", in the "IOC Application Developer's Guide R3.14.1".
 The "Example Application" section briefly explains how to create and build
 an example application in a user created &lt;top> directory. It also explains
 how to run the example application on a vxWorks ioc or a host system and