This document describes how to convert a R3.13 vxWorks application
-so that it builds with release R3.14.0beta1. It describes procedures
+so that it builds with release R3.14.0beta2. It describes procedures
such that:
mkdir <top>
cd <top> -
<full path to R3.14.0beta1 base>/bin/<host_arch>/makeBaseApp.pl +
<full path to R3.14.0beta2 base>/bin/<host_arch>/makeBaseApp.pl -t example example
SNCSEQ =<full path to seq module top>-The R3.14 seq module must exist and be built with EPICS base R3.14.0beta1. +The R3.14 seq module must exist and be built with EPICS base R3.14.0beta2.
Remove any duplicate prodname>_SRCS definitions.
Change LIBOBJS += <seq_program_name>.o
lines
to <prodname>_SRCS += <seq_program_name>.stt
or <prodname>_SRCS += <seq_program_name>.st
Add the lines -
#<name>_LIBS += seq +# <name>_registerRecordDeviceDriver.cpp will be created +from <name>.dbd ++
<name>_SRCS += example_registerRecordDeviceDriver.cpp +#The following adds support from base/src/vxWorks +
<name>_OBJS_vxWorks += $(EPICS_BASE_BIN)/vxComLibrary +#<name>_LIBS += seq
#<name>_LIBS += pv
#seq_DIR = $(SNCSEQ_LIB)
#pv_DIR = $(SNCSEQ_LIB) @@ -154,7 +160,8 @@ where <name> is the name in the PROD_vxWorks definition, and uncomment the first four lines if you have sequence programs (.st or .stt files) in the current directory.Place all macro definitions between the include lines. -
Place any rules after the last include line.
Place any rules after the last include line. +
Remove the file Makefile.Vx.
Change include ARCH = <old arch specification e.g. mv167>
to include ARCH = <new arch specificatio
e.g. vxWorks-68040>
+
Add the following macro definition
+
TARGETS = cdCommands
+
Place all macro definitions between the include lines.
Change include $(TOP)/config/RULES.ioc
to include $(TOP)/configure/RULES.ioc
-
Add the following rule at the end of the Makefile. -
buildInstall: cdCommands- +
If it exists, remove the line
+
buildInstall: cdCommands
+
You will need to add the line "#include "recGbl.h" to +any source files that have recGbl* calls so that the file will compile +without "implicit declaration of function" warnings and the library will +load in the ioc without "undefined symbol: _recGblSetSevr" errors.+
recDynLink.o and devPtSoft.o are no longer in EPICS base and -now exist as separate EPICS modules.You must now add the appropriate module -full path definitions to your application config/RELEASE file, and change -LIBOBJS -location definition $(EPICS_BASE_BIN) to the module definition -bin directory in your application src directory files. See "Hardware -support changes" below for instructions.+now exist as separate EPICS modules. If these are not used in your application, +comment out references to them in base.dbd and baseLIBOBJS. If they are +used, you must now add the appropriate module full path definitions to +your application config/RELEASE file, and change +LIBOBJS location +definition $(EPICS_BASE_BIN) to the module definition bin directory +in your application src directory files. See "Hardware support changes" +below for instructions.
All hardware support (dev, drv and dbd files) except soft support has been unbundled from base R3.14. This support includes the files symb.dbd, drvHp1404a.o, drvEpvxiMsg.o, and drvEpvxi.o. If these are not used by your -application, comment out references to them in base.dbd.+application, comment out references to them in base.dbd and baseLIBOBJS.
Hardware support now exists as separate EPICS modules. The hardware support for your site should be downloaded and built with base @@ -284,10 +304,7 @@ dbLoadtemplate tool changes extension, msi, which should be downloaded and built with base R3.14 by your EPICS administrator. dbLoadTemplate is still supported on iocs. If, in your application, db files are created from template and substitution -files you should add the definition -+files you should must have the msi executable in your path.EPICS_EXTENSIONS=<full -path name to epics extensions directory> -
to your application config/RELEASE file.