From 40e6553dcceae0a575aff707e5db776ac5a312be Mon Sep 17 00:00:00 2001
From: "Janet B. Anderson" Building EPICS R3.13 applications with R3.14.0beta2 base
+Building EPICS R3.13 applications with R3.14.1 base
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:
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.
If you build sequencer programs add the lines
diff --git a/documentation/BuildingR3.13ExtensionsWithR3.14.html b/documentation/BuildingR3.13ExtensionsWithR3.14.html index 9395efbb0..44782bd4b 100644 --- a/documentation/BuildingR3.13ExtensionsWithR3.14.html +++ b/documentation/BuildingR3.13ExtensionsWithR3.14.html @@ -9,7 +9,7 @@
diff --git a/documentation/ConvertingR3.13AppsToR3.14.html b/documentation/ConvertingR3.13AppsToR3.14.html
index 26ba7881b..744ad6ef2 100644
--- a/documentation/ConvertingR3.13AppsToR3.14.html
+++ b/documentation/ConvertingR3.13AppsToR3.14.html
@@ -10,12 +10,12 @@
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:
SNCSEQ =<full path to seq module top>
-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.1If 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.
+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.
- -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.
- --- -// does the local compiler support placement delete
-#if defined (_MSC_VER)
-# if _MSC_VER >= 1200
-# define NETIO_PLACEMENT_DELETE
-# endif
-#elif defined ( __HP_aCC )
-# if _HP_aCC > 033300
-# define NETIO_PLACEMENT_DELETE
-# endif
-#elif defined ( __BORLANDC__ )
-# if __BORLANDC__ > 0x550
-# define NETIO_PLACEMENT_DELETE
-# endif
-#else
-# define NETIO_PLACEMENT_DELETE
-#endif
-
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).
- -// visual c++ 6.0 appears to be sensitive to the
// order of the following four lines
#define VC_EXTRALEAN
#define _WIN32_WINNT 0x400
#include <windows.h>
#include <winsock2.h>
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 <top> directory. It also explains how to run the example application on a vxWorks ioc or a host system and